CVE-2020-36455: Command Injection
First published: Sun Aug 08 2021(Updated: )
An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock<T> unconditionally implements Send and Sync.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| slock | <=2020-11-17 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-36455?
CVE-2020-36455 has a severity level that can lead to potential data races in applications utilizing the slock crate.
How do I fix CVE-2020-36455?
To fix CVE-2020-36455, update the slock crate to a version later than 2020-11-17.
What does CVE-2020-36455 affect?
CVE-2020-36455 affects the slock crate versions up to and including 2020-11-17 for Rust.
What is the risk of using slock with CVE-2020-36455?
Using slock with CVE-2020-36455 may result in unsynchronized access to shared data across threads, leading to unpredictable behavior.
Is CVE-2020-36455 known to be exploited in the wild?
As of now, there have been no public reports of CVE-2020-36455 being actively exploited.
- agent/type
- agent/references
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/author
- agent/last-modified-date
- agent/weakness
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/brokenlamp
- canonical/slock
- version/slock/2020-11-17