CVE-2020-35913
CVE-2020-35913 is a medium-severity vulnerability in Lock Api Project Lock Api with a CVSS 3.x base score of 4.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.
Key facts
- Severity: Medium (CVSS 3.x base score 4.7)
- CVSS v2: 1.9
- EPSS exploit prediction: 0% (10th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-362
- Affected product: Lock Api Project Lock Api
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2020-35913?
- An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.
- How severe is CVE-2020-35913?
- CVE-2020-35913 has a CVSS 3.x base score of 4.7, rated medium severity. It is exploitable over local access with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
- Is CVE-2020-35913 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2020-35913?
- CVE-2020-35913 affects Lock Api Project Lock Api. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2020-35913?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2020-35913 published?
- CVE-2020-35913 was published on 2020-12-31 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:lock_api_project:lock_api:*:*:*:*:*:rust:*:*
More vulnerabilities in Lock Api Project Lock Api
- CVE-2020-35910 — Medium (CVSS 5.5): An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard…
- CVE-2020-35914 — Medium (CVSS 4.7): An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard…
- CVE-2020-35912 — Medium (CVSS 4.7): An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of…
- CVE-2020-35911 — Medium (CVSS 4.7): An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of…
All CVEs affecting Lock Api Project Lock Api →
Other CWE-362 (Race Condition) vulnerabilities
- CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
- CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
- CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
- CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
- CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
- CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…