Vulnerability CriticalRUSTSEC-2021-0036 · internment
RUSTSEC-2021-0036: Intern<T>: Data race allowed on T
Short answerA security vulnerability in the internment crate: Intern<T>: Data race allowed on T. Critical severity (CVSS 9.8). Fixed in 0.4.2: update to a fixed version.
| Crate | internment |
|---|---|
| Type | Vulnerability (thread-safety) |
| Affected versions | Before 0.4.2. |
| Fixed in | 0.4.2 |
| 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 | 2021-03-03 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2021-28037, GHSA-gppw-3h6h-v6q2 |
What to do
- See which version you have:
cargo tree -i internment(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p internment. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleinternment = "0.4.2") 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 this crate unconditionally implements Sync for Intern<T>. This allows users to create data race on T: !Sync, which may lead to undefined behavior (for example, memory corruption).
The flaw was corrected in commit 2928a87 by adding the trait bound T: Sync in the Sync impl of Intern<T>.
References
- Package: crates.io/crates/internment
- Advisory: rustsec.org/advisories/RUSTSEC-2021-0036.html
- Report: github.com/droundy/internment/issues/20
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for internment
Up next
Same crateinternment: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?