Fuzzing 101
summary
Practical guide to fuzz testing using AddressSanitizer together with libFuzzer, AFL, or Honggfuzz; recommends in-memory fuzzing for high iteration rates and starting with a small diverse seed corpus (3–20 files) that is minimized twice. Presents evidence from OSS-Fuzz and Google Project Zero showing many real bugs found by fuzzing, and notes fuzzing scales roughly linearly with CPU cores so running bursty cloud workers is an effective way to find bugs.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:16Software security problems
- 10:09What is fuzzing and its benefits
- 17:15Fuzzing basics
- 21:51Eight fuzzing laws
- 25:43Language testing
- 32:07Function-level testing
- 37:12Open source integration
- 42:06Unit test fuzzing
- 45:43Binary black-box testing
- 48:36CI/CD fuzzing integration
- 50:44Fast tests with OSS-Fuzz
related talks
25mHow fuzzing helps to find bugs
31m“Fuzz or lose..."
01h 15mMake your programs more reliable with Fuzzing
39mMaking Fuzzing Part of Your Software Development Lifecycle
24mWhy you should be using automated fuzzing to test for security issues in your code
01h 00mClusterFuzz: Fuzzing at Google Scale
44mOSS-Fuzz - Google's continuous fuzzing service for open source software
21mModern Testing and Fuzzing in Bitcoin Core