CVE-2017-20004

In the standard library in Rust before 1.19.0, there is a synchronization problem in the MutexGuard object. MutexGuards can be used across threads with any types, allowing for memory safety issues through race conditions.

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

CVE-2017-20004 is rated Low Risk (38.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.24%). 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-2017-20004

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 2025-03-30 0.83% 0.24% -0.58%
2 2025-03-29 0.24% 0.83% +0.58%
3 2025-03-17 — 0.24% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-20004

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.9 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
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:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
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:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2017-20004

OS Trackers for CVE-2017-20004

vendor priority summary link
debian not yet assigned CVE-2017-20004 not yet assigned priority: Debian including 1 source packages (rustc), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-20004
redhat medium — https://access.redhat.com/security/cve/CVE-2017-20004
ubuntu medium CVE-2017-20004 medium priority: Ubuntu including 1 source packages (rustc), 6 status rows across 6 suites (bionic, focal, groovy, trusty, upstream, xenial): not-affected 5, released 1. https://ubuntu.com/security/CVE-2017-20004

Affected software / configurations for CVE-2017-20004

Vendor Product Version Raw CPE
rust-lang rust < 1.19.0 cpe:2.3:a:rust-lang:rust:*:*:*:*:*:*:*:*

References for CVE-2017-20004

URL Tags
https://github.com/rust-lang/rust/issues/41622 Patch Third Party Advisory
https://github.com/rust-lang/rust/pull/41624 Patch Third Party Advisory
cvelogic Threat Intelligence