CVE-2020-36472 json
Data races in max7301
published 2020-12-18 5 y ago modified 2026-06-17 4 mo ago also GHSA-rmff-f8w9-c9rm , RUSTSEC-2020-0152 , EUVD-2021-1872
- cvss
- 5.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
An issue was discovered in the max7301 crate before 0.2.0 for Rust. The ImmediateIO and TransactionalIO types implement Sync for all Expander<EI> types that they contain.
Patch / fix
- crates.io max7301 0.2.0
- max7301_project max7301 0.2.0
Exploit prediction
0.98% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- rustsec.org https://rustsec.org/advisories/RUSTSEC-2020-0152.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | max7301 | <0.2.0 >=0.0.0-0, <0.2.0 |
0.2.0 |
Classification
- Weakness
-
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
References
-
rustsec.org
/advisories/RUSTSEC-2020-0152.html
web, exploit, issue-tracking, patch, third-party-advisory, advisory
-
github.com
/edarc/max7301/commit/0a1da873ddb29bca926bad8301f8d7ab8aa97c52
web
-
raw.githubusercontent.com
/rustsec/advisory-db/main/crates/max7301/RUSTSEC-2020-0152.md
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-36472
advisory
-
github.com
/edarc/max7301/issues/1
web, report
-
github.com
/edarc/max7301
package
-
crates.io
/crates/max7301
package
Sources
- CVE List CVE-2020-36472
- GitHub Advisory GHSA-rmff-f8w9-c9rm
- NVD CVE-2020-36472
- OSV RUSTSEC-2020-0152
Fencer Vulns 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.