Add AFL++ fuzzing test crate and docs - #2016
Draft
leighmcculloch wants to merge 3 commits into
Draft
Conversation
leighmcculloch
force-pushed
the
afl-fuzz-test-crate
branch
from
August 19, 2026 13:13
d65e3a6 to
9748b6e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add a
tests/fuzz_aflcrate that fuzzes a Soroban contract with afl.rs, with a README that walks a first-time fuzzer through setup, running a campaign, reading the AFL++ UI, and reproducing a crash, and document the same workflow in thetestutils::arbitrarymodule.Why
The arbitrary module only explained fuzzing via
cargo-fuzz/libFuzzer, so contract authors using AFL++ had no supported harness pattern or worked example to copy.Known limitations
The fuzz harness lives in its own workspace and is built by
make build-fuzz-afl, which requirescargo-afland a C compiler, so it is not part of the default build or CI.SemVer Change
vX._._) - Breaking change to the public API.v_.Y._) - Additive change to the public API.v_._.Z) - No change to the public API.