How severe is CVE-2020-35910?

CVE-2020-35910 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2020-35910 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-35910?

CVE-2020-35910 affects Lock Api Project Lock Api. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-35910?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2020-35910 published?

CVE-2020-35910 was published on 2020-12-31 and last updated on 2026-06-17.

CVE-2020-35910

CVE-2020-35910 is a medium-severity vulnerability in Lock Api Project Lock Api with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 5.5)
CVSS v2: 2.1
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Lock Api Project Lock Api
Published: 2020-12-31
Last modified: 2026-06-17

Description

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

Frequently asked questions

What is CVE-2020-35910?: An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness.
How severe is CVE-2020-35910?: CVE-2020-35910 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2020-35910 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-35910?: CVE-2020-35910 affects Lock Api Project Lock Api. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-35910?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-35910 published?: CVE-2020-35910 was published on 2020-12-31 and last updated on 2026-06-17.

References

https://rustsec.org/advisories/RUSTSEC-2020-0070.html

Affected products (1)

cpe:2.3:a:lock_api_project:lock_api:*:*:*:*:*:rust:*:*

More vulnerabilities in Lock Api Project Lock Api

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-35913 — 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 RwLockReadGuard…
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 →