fuzzing-obstacles

Featured

Techniques for patching code to overcome fuzzing obstacles. Use when checksums, global state, or other barriers block fuzzer progress.

Testing & QA 8,273 stars 715 forks Updated 6 days ago CC-BY-SA-4.0

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Overcoming Fuzzing Obstacles Codebases often contain anti-fuzzing patterns that prevent effective coverage. Checksums, global state (like time-seeded PRNGs), and validation checks can block the fuzzer from exploring deeper code paths. This technique shows how to patch your System Under Test (SUT) to bypass these obstacles during fuzzing while preserving production behavior. ## Overview Many real-world programs were not designed with fuzzing in mind. They may: - Verify checksums or cryptographic hashes before processing input - Rely on global state (e.g., system time, environment variables) - Use non-deterministic random number generators - Perform complex validation that makes it difficult for the fuzzer to generate valid inputs These patterns make fuzzing difficult because: 1. **Checksums:** The fuzzer must guess correct hash values (astronomically unlikely) 2. **Global state:** Same input produces different behavior across runs (breaks determinism) 3. **Complex validation:** The fuzzer spends effort hitting validation failures instead of exploring deeper code The solution is conditional compilation: modify code behavior during fuzzing builds while keeping production code unchanged. ### Key Concepts | Concept | Description | |---------|-------------| | SUT Patching | Modifying System Under Test to be fuzzing-friendly | | Conditional Compilation | Code that behaves differently based on compile-time flags | | Fuzzing Build Mode | Special build configuration that enabl...

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

Data & Documents Listed

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.

719 Updated 3 months ago
0xwilliamortiz
Data & Documents Featured

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.

11,204 Updated yesterday
SnailSploit
AI & Automation Listed

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.

0 Updated 5 days ago
umbrasec-labs