Stack overflow detected during fuzzing
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 869
- Forks
- 152
- Avg merge
- 15h 8m
- Merged PRs (30d)
- 12
Description
While fuzzing the cssparser fuzz target I encountered a stack overflow leading to a core dump.
The overflow occurs when the input contains ~17500 (or more) opening brackets, i.e., (, [, {.
I attached an example input that was generated by the fuzzer.
64a4f3d80c6f9598cfc40255f7410db68675019d5c2be9eb5555ca5721c29516.txt
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 cssparser fuzz target and reproduce the crash using the attached input, which contains about 17,500 opening brackets. Trace the stack overflow in the parser and add regression coverage; done means the input no longer causes a stack overflow or core dump.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100