PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Master fuzzing with our new Testing Handbook chapter

blog.trailofbits.com | blog | #fuzzing | #rust | #testing | #libfuzzer | #addresssanitizer | #afl | #cargo-fuzz
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

Trail of Bits' new Testing Handbook chapter covers fuzzing C/C++ and Rust with libFuzzer, AFL++, and cargo-fuzz, including harness writing, fuzzing dictionaries, and AddressSanitizer usage.
Published
Collected

Related coverage

blog · blog.trailofbits.com
DeepState Now Supports Ensemble Fuzzing
DeepState, Trail of Bits' fuzzing and symbolic execution testing framework, now supports ensemble fuzzing—running multiple fuzzers with different heuristics and syncing seeds across them.
blog · blog.trailofbits.com
Rust-proof your code with our new Testing Handbook chapter
Trail of Bits added a Rust testing chapter to its Testing Handbook: Miri, property testing, Clippy, zeroization, Kani model checking and dependency vetting, plus the rust-review Claude Code plugin.
blog · blog.trailofbits.com
Introducing Ruzzy, a coverage-guided Ruby fuzzer
Trail of Bits released Ruzzy, a coverage-guided fuzzer for pure Ruby and Ruby C extensions, built on libFuzzer with Atheris inspiration and ASan/UBSan support to find DoS and memory corruption bugs.
blog · blog.trailofbits.com
The Smart Fuzzer Revolution
Dan Guido's BSidesLisbon keynote contextualizes AFL, libFuzzer, the DARPA Cyber Grand Challenge, and Project Springfield, tracing recent leaps in automated bug finding and their industry impact.
blog · blog.trailofbits.com
Making PyPI's test suite 81% faster
Trail of Bits cut PyPI's Warehouse test suite from 163 to 30 seconds via pytest-xdist parallelization, Python 3.12 sys.monitoring coverage, optimized test discovery, and trimmed imports.
blog · blog.trailofbits.com
Understanding AddressSanitizer: Better memory safety for your code
Trail of Bits explains how AddressSanitizer works, covering shadow memory, redzones, container annotations, limitations, and false positives, plus the LLVM contributions these findings produced.
Back