Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

afl-fuzz: initial corpus is always created even if already exists #36

Open
fuzzah opened this issue Nov 13, 2024 · 0 comments
Open

afl-fuzz: initial corpus is always created even if already exists #36

fuzzah opened this issue Nov 13, 2024 · 0 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@fuzzah
Copy link
Member

fuzzah commented Nov 13, 2024

bb-fuzz checks if there's anything in the input dir, but the check is implemented improperly (in corpus_utils.py), as os.listdir() returns only names, but not relative paths.
This results in creating initial "corpus" every single time, even when it already exists.

It's a problem, because some fuzz targets don't run instrumented code if the sample is too short (i.e. partially instrumented apps such as .NET). And when such sample exists in the input dir, afl-fuzz can't start, as it detects no instrumentation on this one sample 🤷

@fuzzah fuzzah added bug Something isn't working good first issue Good for newcomers labels Nov 13, 2024
fuzzah added a commit that referenced this issue Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant