Vulnerability CriticalRUSTSEC-2020-0007 · bitvec
RUSTSEC-2020-0007: use-after or double free of allocated memory
Short answerA security vulnerability in the bitvec crate: use-after or double free of allocated memory. Critical severity (CVSS 9.8). Fixed in 0.17.4: update to a fixed version.
| Crate | bitvec |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | From 0.11.0 before 0.17.4. |
| Fixed in | 0.17.4 |
| Severity | Critical, CVSS 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | 2020-03-27 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-35862, GHSA-7cjc-hvxf-gqh7 |
| Affected functions | bitvec::vec::BitVec::into_boxed_bitslice |
What to do
- See which version you have:
cargo tree -i bitvec(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p bitvec. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplebitvec = "0.17.4") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Conversion of BitVec to BitBox did not account for allocation movement.
The flaw was corrected by using the address after resizing, rather than the original base address.
References
- Package: crates.io/crates/bitvec
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0007.html
- Report: github.com/myrrlyn/bitvec/issues/55
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Same cratebitvec: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?