trailofbits / trailofbits/testing-handbook
rust fuzzing - more info for sanitizers
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 135
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
We can write more about advances sanitizer use-cases for rust fuzzing (https://appsec.guide/docs/fuzzing/rust/):
- instrument only C bindings and not rust code, like in https://maxammann.org/posts/2021/06/sanitize-rust-sys-crate/
- instrument rust std lib as recommended in https://doc.rust-lang.org/beta/unstable-book/compiler-flags/sanitizer.html#instrumentation-of-external-dependencies-and-std
- instrument only parts of Rust code (selected Rust functions or only unsafe code) to better guide the fuzzing
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Rust fuzzing page at https://appsec.guide/docs/fuzzing/rust/ and review the linked sanitizer references. Expand the page with accurate guidance for instrumenting C bindings, Rust’s standard library, and selected Rust code or unsafe code. Done means these three use cases are clearly explained with the relevant links and practical scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100