Lock Api Project maintains a specialized synchronization library that, despite narrow product scope, serves as a foundational component in concurrent programming contexts where its use is critical. The vendor's vulnerability signal centers on the inherent challenges of shared-resource synchronization, with observed issues reflecting race conditions and related concurrency weaknesses that arise in low-level locking abstractions. Current severity, exploitation activity, and exposure metrics are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Lock Api Project over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-35910MEDIUM An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness. | Dec 31, 2020 | 5.5 | 18 | NO | NO |
CVE-2020-35914MEDIUM An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness. | Dec 31, 2020 | 4.7 | 17 | NO | NO |
CVE-2020-35913MEDIUM An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness. | Dec 31, 2020 | 4.7 | 17 | NO | NO |
CVE-2020-35912MEDIUM An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness. | Dec 31, 2020 | 4.7 | 17 | NO | NO |
CVE-2020-35911MEDIUM An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness. | Dec 31, 2020 | 4.7 | 17 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Lock Api Project.
Media articles that mention a CVE ID that affects a product developed by Lock Api Project — matched by CVE ID, not by vendor name.