fuzzing-obstacles
FeaturedTechniques for patching code to overcome fuzzing obstacles. Use when checksums, global state, or other barriers block fuzzer progress.
Install
Quality Score: 93/100
Skill Content
Details
- Author
- trailofbits
- Repository
- trailofbits/skills
- Created
- 10 months ago
- Last Updated
- 6 days ago
- Language
- Python
- License
- CC-BY-SA-4.0
Similar Skills
Semantically similar based on skill content — not just same category
offensive-fuzzing
Practical offensive fuzzing methodology covering target identification, fuzzer selection (AFL++, libFuzzer, Honggfuzz, Boofuzz, syzkaller), harness writing, corpus curation, mutation strategies, coverage measurement, and crash triage. Use when setting up or running fuzz campaigns against any target: file parsers, network protocols, kernel drivers, EDR engines, embedded firmware, or language runtimes.
offensive-fuzzing
Practical offensive fuzzing methodology covering target identification, fuzzer selection (AFL++, libFuzzer, Honggfuzz, Boofuzz, syzkaller), harness writing, corpus curation, mutation strategies, coverage measurement, and crash triage. Use when setting up or running fuzz campaigns against any target: file parsers, network protocols, kernel drivers, EDR engines, embedded firmware, or language runtimes.
integrate-fuzzing-sdlc
Defensive methodology for building fuzzing into your SDLC and CI so you find exploitable memory-safety and parsing bugs in your own code before an adversary fuzzes your released binaries to develop exploits (MITRE ATT&CK T1587.004, which names fuzzing, feeding T1190, T1203, and T1068). The log source is your build pipeline, not a SIEM: sanitizer reports (ASan, UBSan, MSan, TSan), libFuzzer and AFL++ crash output, OSS-Fuzz / ClusterFuzz / CIFuzz dashboards, coverage deltas, and crash stack-hash dedup in GitHub Actions or GitLab CI. Gives the signals, a CI gating approach, a corpus-triage hunt, and SDLC hardening mapped to ISO and NIST. Use when you want to add fuzzing to CI, triage a fuzzer crash, dedup and bug-bucket findings, decide whether a sanitizer report is exploitable and release-blocking, set up OSS-Fuzz or CIFuzz, or harden a library release process against bug-hunting attackers.