PatchTheCVECVE-2020-36455: An issue was discovered in the slock crate through 2020-11-17 for Rust
CVE-2020-36455 is a high-severity flaw (CVSS 8.1) affecting slock. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock<T> unconditionally implements Send and Sync.
Why this priority
- High severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.1 (High) |
| Attack vector | Network (remote) |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.3% (top 29%) |
| CISA exploited list | No |
| Weakness | CWE-77 |
| Published | 2021-08-08 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2020-36455?
slock: upgrade to newer than 2020-11-17. Exact commands for each OS are on this page.
Is CVE-2020-36455 being exploited?
CVE-2020-36455 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2020-36455 affect?
CVE-2020-36455 affects slock. Severity is high (CVSS 8.1). An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock<T> unconditionally implements Send and Sync.
How urgent is CVE-2020-36455?
Priority 56/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action
Related CVEs
- CVE-2016-6866 HIGH 7.5 UPGRADE MITIGATE slock allows attackers to bypass the screen lock via vectors involving an invalid password hash, which trigger