Skip to content

Conversation

sigaloid
Copy link
Contributor

Fuzzing is important for any parser that strives to be panic-free!

@sigaloid
Copy link
Contributor Author

sigaloid commented Jul 10, 2024

image

In just 10 seconds it found a ton of crashes! I won't file an issue for these as you, the maintainer, knows best what's truly an issue. But here's how to reproduce this:

cargo install cargo-afl
cd afl-fuzz/
cargo afl build --release
cargo afl fuzz -i ../testdata/ -o out target/release/afl-fuzz

(Your testdata directory is really great for seeding the fuzzer - initial states drastically improve the odds of the fuzzer finding a crash!)

Then as it finds more crashes, they will appear in out/default/crashes/*. You can reproduce an individual one and find the exact panic message like so:

cargo afl run ./target/release/afl-fuzz < out/default/crashes/[CRASH_INPUT]

@mindeng mindeng merged commit e20d892 into mindeng:main Jul 11, 2024
@mindeng
Copy link
Owner

mindeng commented Jul 11, 2024

Great! I will run the fuzzing test and fix the crash issues.

Thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants