Rust advisories / atom
Unsound MediumRUSTSEC-2020-0044 · atom
RUSTSEC-2020-0044: Unsafe Send implementation in Atom allows data races
Short answeratom has an API that can cause undefined behaviour from safe code: Unsafe Send implementation in Atom allows data races. Fixed in 0.3.6.
| Crate | atom |
|---|---|
| Type | Unsound (thread-safety) |
| Affected versions | Before 0.3.6. |
| Fixed in | 0.3.6 |
| Severity | Medium, CVSS 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
| Published | 2020-09-21 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-35897, GHSA-9cg2-2j2h-59v9 |
What to do
- See which version you have:
cargo tree -i atom(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p atom. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleatom = "0.3.6") 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
The atom crate contains a security issue revolving around its implementation of the Send trait. It incorrectly allows any arbitrary type to be sent across threads potentially leading to use-after-free issues through memory races.
References
- Package: crates.io/crates/atom
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0044.html
- Report: github.com/slide-rs/atom/issues/13
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?