Rust advisories / hashconsing
Vulnerability HighRUSTSEC-2020-0107 · hashconsing
RUSTSEC-2020-0107: hashconsing's HConsed lacks Send/Sync bound for its Send/Sync trait.
Short answerA security vulnerability in the hashconsing crate: hashconsing's HConsed lacks Send/Sync bound for its Send/Sync trait.. High severity (CVSS 7.5). Fixed in 1.1.0: update to a fixed version.
| Crate | hashconsing |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Before 1.1.0. |
| Fixed in | 1.1.0 |
| Severity | High, CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| Published | 2020-11-10 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36215, GHSA-rw2c-c256-3r53 |
What to do
- See which version you have:
cargo tree -i hashconsing(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p hashconsing. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplehashconsing = "1.1.0") 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
Affected versions of hashconsing implements Send/Sync for its HConsed type without restricting it to Sendable types and Syncable types.
This allows non-Sync types such as Cell to be shared across threads leading to undefined behavior and memory corruption in concurrent programs.
References
- Package: crates.io/crates/hashconsing
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0107.html
- Report: github.com/AdrienChampion/hashconsing/issues/1
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
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?