CVE-2020-36455
Slock<T> allows sending non-Send types across thread boundaries
An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock<T> unconditionally implements Send and Sync.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock<T> unconditionally implements Send and Sync.
- Record
CVE-2020-36455- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS 2.0
- 5.1 Medium
AV:N/AC:H/Au:N/C:P/I:P/A:P - Weakness
- CWE-77
- Updated
- 2026-11-02
CVE List No score
An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock<T> unconditionally implements Send and Sync.
- Record
CVE-2020-36455- Updated
- 2026-11-02
EUVDEUVD-2021-1797 No score
An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock<T> unconditionally implements Send and Sync.
- Record
EUVD-2021-1797- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-83r8-p8v6-6gfm
Slock<T> allows sending non-Send types across thread boundaries
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.
- Record
GHSA-83r8-p8v6-6gfm- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-362
- Updated
- 2026-11-02
GitHub AdvisoriesGHSA-mc36-5m36-hjh5
Data races in slock
An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock<T> unconditionally implements Send and Sync.
- Record
GHSA-mc36-5m36-hjh5- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-77, CWE-362
- Updated
- 2026-11-02
OSVGHSA-83r8-p8v6-6gfm
Slock<T> allows sending non-Send types across thread boundaries
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.
- Record
GHSA-83r8-p8v6-6gfm- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-362
- Updated
- 2026-11-02
OSVGHSA-mc36-5m36-hjh5
Data races in slock
An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock<T> unconditionally implements Send and Sync.
- Record
GHSA-mc36-5m36-hjh5- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-362, CWE-77
- Updated
- 2026-11-02
OSVRUSTSEC-2020-0135
Slock<T> allows sending non-Send types across thread boundaries
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.
- Record
RUSTSEC-2020-0135- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
Affected products
Affected packages
History
| Recorded | Changed | Sources |
|---|---|---|
| facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2020-36455 is a high vulnerability (CVSS 8.1) in Brokenlamp Slock, published November 17, 2020. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.31%, the 71st percentile. Fixed in slock 0.2.0.
References
rustsec.org/advisories/RUSTSEC-2020-0135.html
raw.githubusercontent.com/rustsec/advisory-db/main/crates/slock/RUSTSEC-2020-0135.md
github.com/BrokenLamp/slock-rs/issues/2
nvd.nist.gov/vuln/detail/CVE-2020-36455
crates.io/crates/slock