Memory corruption fixed in smallvec 2.0.0-alpha-6
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.2k
- Forks
- 544
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 45
Description
According to https://github.com/servo/rust-smallvec/issues/353, there was a memory corruption in smallvec 2.0.0-alpha.5. I didn't check the range of affected versions, although that bug report mentions that:
Smallvec 1.x works fine.
I don't know what's the policy for vulnerabilities in pre-release versions, but given that smallvec is used a lot (and the 2.0.0-alpha.x branch already has 8 reverse dependencies according to https://lib.rs/crates/smallvec/rev), it may be worth recording that in the advisory database.
Perhaps using the version range >= 2.0.0 <= 2.0.0-alpha.5 to be conservative (I'm not sure how the tool works w.r.t. version suffixes)?
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 with the linked smallvec issue #353 and verify which pre-release versions were affected, including how the advisory tooling interprets version suffixes. Done means the advisory database contains a reviewed entry with a confirmed affected range and vulnerability details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100