Rust advisories / lever
Vulnerability HighRUSTSEC-2020-0137 · lever
RUSTSEC-2020-0137: AtomicBox<T> lacks bound on its Send and Sync traits allowing data races
Short answerA security vulnerability in the lever crate: AtomicBox<T> lacks bound on its Send and Sync traits allowing data races. High severity (CVSS 8.1). Fixed in 0.1.1: update to a fixed version.
| Crate | lever |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Before 0.1.1. |
| Fixed in | 0.1.1 |
| Severity | High, CVSS 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | 2020-11-10 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36457, GHSA-9pp4-8p8v-g78w |
What to do
- See which version you have:
cargo tree -i lever(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p lever. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplelever = "0.1.1") 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
AtomicBox<T> is a Box type designed to be used across threads, however, it implements the Send and Sync traits for all types T.
This allows non-Send types such as Rc and non-Sync types such as Cell to be used across thread boundaries which can trigger undefined behavior and memory corruption.
References
- Package: crates.io/crates/lever
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0137.html
- Report: github.com/vertexclique/lever/issues/15
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?