CVE-2020-35924 json
Data races in try-mutex
published 5y ago modified 4mo ago also GHSA-64j8-7gp2-xjx5 , RUSTSEC-2020-0087 , EUVD-2021-1589
- cvss
- 5.5
- 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 32%
- public exploits
- 0
- none known
Summary
An issue was discovered in the try-mutex crate before 0.3.0 for Rust. TryMutex<T> allows cross-thread sending of a non-Send type.
Patch / fix
- crates.io try-mutex 0.3.0
- try-mutex_project try-mutex 0.3.0
Is CVE-2020-35924 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.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- rustsec.org https://rustsec.org/advisories/RUSTSEC-2020-0087.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:N/A:P |
| OSV | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | try-mutex | <0.3.0 >=0.0.0-0, <0.3.0 |
0.3.0 |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
rustsec.org
/advisories/RUSTSEC-2020-0087.html
web, exploit, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35924
advisory
-
github.com
/mpdn/try-mutex/issues/2
web, report
-
github.com
/mpdn/try-mutex
package
-
crates.io
/crates/try-mutex
package
Sources
- CVE List CVE-2020-35924
- GitHub Advisory GHSA-64j8-7gp2-xjx5
- NVD CVE-2020-35924
- OSV RUSTSEC-2020-0087
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.