CVE-2020-35912

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

Published: 2020-12-31 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-35912 is rated Low Risk (22.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.21%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-35912

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.04% 0.21% +0.16%
2 2025-03-30 0.06% 0.04% -0.02%
3 2025-03-29 — 0.06% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-35912

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.0 3.6 [email protected]
1.9 2.0 LOW
AV:L/AC:M/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 3.4 2.9 [email protected]

Weakness enumeration for CVE-2020-35912

GitHub Security Advisory for CVE-2020-35912

OS Trackers for CVE-2020-35912

vendor priority summary link
debian not yet assigned CVE-2020-35912 not yet assigned priority: Debian including 2 source packages (rust-lock-api, rust-lock-api-0.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 2. https://security-tracker.debian.org/tracker/CVE-2020-35912
ubuntu low CVE-2020-35912 low priority: Ubuntu including 1 source packages (rust-lock-api), 16 status rows across 16 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 8, needs-triage 5, DNE 3. https://ubuntu.com/security/CVE-2020-35912

Affected software / configurations for CVE-2020-35912

Vendor Product Version Raw CPE
lock_api_project lock_api < 0.4.2 cpe:2.3:a:lock_api_project:lock_api:*:*:*:*:*:rust:*:*

References for CVE-2020-35912

cvelogic Threat Intelligence