CVE-2021-29939 json
Out of bounds write in stackvector
published 2021-02-19 5 y ago modified 2026-06-17 4 mo ago also GHSA-9frf-r7c7-j2vg , RUSTSEC-2021-0048 , EUVD-2021-1659
- cvss
- 7.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
An issue was discovered in the stackvector crate through 2021-02-19 for Rust. There is an out-of-bounds write in StackVec::extend if size_hint provides certain anomalous data.
Patch / fix
- crates.io stackvector 1.0.9
- stackvector_project stackvector 1.0.9
- rust-stackvector Debian 14, Debian 13, Debian 12 1.0.6-3
debian advisories DEBIAN-CVE-2021-29939
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
1.03% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- rustsec.org https://rustsec.org/advisories/RUSTSEC-2021-0048.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| OSV | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
| GitHub | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | stackvector | <1.0.9 >=0.0.0-0, <1.0.9 |
1.0.9 |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
rustsec.org
/advisories/RUSTSEC-2021-0048.html
web, exploit, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-29939
advisory
-
github.com
/Alexhuszagh/rust-stackvector/issues/2
web, report
-
github.com
/Alexhuszagh/rust-stackvector
package
-
crates.io
/crates/stackvector
package
Sources
- CVE List CVE-2021-29939
- GitHub Advisory GHSA-9frf-r7c7-j2vg
- NVD CVE-2021-29939
- OSV RUSTSEC-2021-0048
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.