CVE-2020-35913

Description

An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.

Category

4.7
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.04%
Third-Party Advisory rustsec.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://rustsec.org/advisories/RUSTSEC-2020-0070.html third party advisory

Frequently Asked Questions

What is the severity of CVE-2020-35913?
CVE-2020-35913 has been scored as a medium severity vulnerability.
How to fix CVE-2020-35913?
To fix CVE-2020-35913, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-35913 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-35913 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.