MozillaSecurity / MozillaSecurity/FuzzManager
[FTB] Generated signatures for assertions should use exact match on crashAddress=0x0
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 208
- Forks
- 48
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 2
Description
Currently we generate signatures matching crashAddress < 0x100 for null deref crashes. Assertions always crash on 0x0, so it would be cheaper to check for an exact match if we also see an assertion message. We should change our signature generation algorithm to do this.
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 by locating the signature generation algorithm and the code that handles assertion messages. Confirm how crashAddress ranges are currently generated, then make the exact 0x0 case conditional on an assertion message while preserving the existing range behavior for other null dereferences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100