CVE-2020-36209 json
Data races in late-static
published 5y ago modified 4mo ago also GHSA-wr55-mf5c-hhwm , RUSTSEC-2020-0102 , EUVD-2021-1921
- cvss
- 7.0
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
An issue was discovered in the late-static crate before 0.4.0 for Rust. Because Sync is implemented for LateStatic with T: Send, a data race can occur.
Patch / fix
- crates.io late-static 0.4.0
- late-static_project late-static 0.4.0
Is CVE-2020-36209 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- rustsec.org https://rustsec.org/advisories/RUSTSEC-2020-0102.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.4 | AV:L/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | late-static | <0.4.0 >=0.0.0-0, <0.4.0 |
0.4.0 |
Classification
- Weakness
-
- CWE-662 Improper Synchronization
References
-
github.com
/Richard-W/late-static/commit/11f396c
web
-
rustsec.org
/advisories/RUSTSEC-2020-0102.html
web, exploit, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-36209
advisory
-
github.com
/Richard-W/late-static/issues/1
web, report
-
github.com
/Richard-W/late-static
package
-
crates.io
/crates/late-static
package
Sources
- CVE List CVE-2020-36209
- GitHub Advisory GHSA-wr55-mf5c-hhwm
- NVD CVE-2020-36209
- OSV RUSTSEC-2020-0102
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.