trailofbits / trailofbits/buttercup
Track PoV origin in redis
Open
Nobody has claimed this yet.
fuzzer
seedgen
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 185
- Avg merge
- 51m
- Merged PRs (30d)
- 1
Description
When submitting PoVs to the crash queue, there should be metadata to track if the PoV origin is the fuzzer or seed-gen. This would make it easier to understand the contribution of each component without needing access to logs.
Contributor guide
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 by locating the code that submits PoVs to the crash queue and stores them in Redis. Trace how the fuzzer and seed-gen origins are represented at submission time, then verify that the stored metadata distinguishes both origins without requiring logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, redis
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100