Rust advisories / slock
Vulnerability HighRUSTSEC-2020-0135 · slock
RUSTSEC-2020-0135: Slock<T> allows sending non-Send types across thread boundaries
Short answerA security vulnerability in the slock crate: Slock<T> allows sending non-Send types across thread boundaries. High severity (CVSS 8.1). Fixed in 0.2.0: update to a fixed version.
| Crate | slock |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Before 0.2.0. |
| Fixed in | 0.2.0 |
| 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-17 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36455, GHSA-83r8-p8v6-6gfm, GHSA-mc36-5m36-hjh5 |
What to do
- See which version you have:
cargo tree -i slock(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p slock. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleslock = "0.2.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
Slock<T> unconditionally implements Send/Sync.
Affected versions of this crate allows sending non-Send types to other threads, which can lead to data races and memory corruption due to the data race.
References
- Package: crates.io/crates/slock
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0135.html
- Report: github.com/BrokenLamp/slock-rs/issues/2
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?