How to Break, Then Fix, Differential Privacy on Finite Computers
summary
Shows that naive floating-point Laplace implementations leak exact counts via precision-based attacks because some floats are unreachable, letting an adversary distinguish 100 vs 101. Tests find multiple open-source libraries affected, two still vulnerable and one fixed (opDP/Growth-like fixes). Presents a provable fix: generate the rounded sample directly using inverse-CDF interval sampling with arbitrary-precision floats/ARB, sampling many bits per iteration so it almost always finishes in one or two steps, preserves privacy without a discretization parameter and works in practice.
AI-written summary · about
chapters (7)
- 0:00Differential privacy vulnerabilities
- 1:33Floating point breaks Laplace
- 3:39Why standard random number generators fail
- 5:25Noise precision loss
- 8:34Fix for floating point issues
- 12:27Inverse CDF sampling fix
- 13:32Key takeaways and libraries
related talks
32mYou've got trust issues, we've got solutions: Differential Privacy
27mVerified Differential Privacy for Finite Computers
58mLarge-Scale Private Learning, Part III
01h 00mDifferential Privacy: Fundamentals to Forefront I
43mDifferential Privacy Meets Robust Statistics
29mSecure, Precise, and Fast Floating-Point Operations on x86 Processors
26mA Framework for Adversarial Streaming via Differential Privacy and Difference Estimators
38mDemystifying Privacy Preserving Computing
