igvm: audit panics to make sure none of them can be hit when parsing unsantized data
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 155
- Forks
- 42
- Avg merge
- 23h 53m
- Merged PRs (30d)
- 3
Description
While we have some panics for internal data where it should have already been sanitized, we need to make sure we don't panic instead of returning an error with context for invalid data (such as converting sizes to u32s, etc).
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
No files, tests, or entry points are named. Start by locating the Rust parsing paths and auditing panic sites reachable from unsanitized input, including size conversions; done means invalid data returns an error with useful context instead of panicking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100