CVE-2020-35910 json
Data races in lock_api
published 6y ago modified 4mo ago also CVE-2020-35911 , CVE-2020-35912 , CVE-2020-35913 , CVE-2020-35914 , GHSA-5wg8-7c9q-794v , GHSA-gmv4-vmx3-x9f3 , GHSA-hj9h-wrgg-hgmx , GHSA-ppj3-7jw3-8vc4 , GHSA-vh4p-6j7g-f4j9 , RUSTSEC-2020-0070 , EUVD-2021-1825
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness.
Patch / fix
- crates.io lock_api 0.4.2
- lock_api_project lock_api 0.4.2
- rust-lock-api Debian 14, Debian 13, Debian 12 0.4.5-1
debian advisories DEBIAN-CVE-2020-35910
- github.com/Amanieu/parking_lot@7de94f9 commit
- github.com/Amanieu/parking_lot#262 pull request
- rustsec.org/advisories/RUSTSEC-2020-0070.html advisory
Is CVE-2020-35910 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.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 |
| GitHub | 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 | 4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | lock_api | <0.4.2 >=0.0.0-0, <0.4.2 |
0.4.2 |
Classification
- Weakness
-
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
References
-
rustsec.org
/advisories/RUSTSEC-2020-0070.html
web, patch, third-party-advisory, advisory
-
github.com
/Amanieu/parking_lot/pull/262
web
-
github.com
/Amanieu/parking_lot/commit/7de94f95f519d8281cb48457964065b463d26736
web
-
nvd.nist.gov
/vuln/detail/CVE-2020-35910
advisory
-
github.com
/Amanieu/parking_lot
package
-
nvd.nist.gov
/vuln/detail/CVE-2020-35913
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35912
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35914
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35911
advisory
-
crates.io
/crates/lock_api
package
Sources
- CVE List CVE-2020-35910
- GitHub Advisory GHSA-ppj3-7jw3-8vc4
- GitHub Advisory GHSA-hj9h-wrgg-hgmx
- GitHub Advisory GHSA-5wg8-7c9q-794v
- GitHub Advisory GHSA-gmv4-vmx3-x9f3
- GitHub Advisory GHSA-vh4p-6j7g-f4j9
- NVD CVE-2020-35910
- OSV RUSTSEC-2020-0070
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.