lock_api
crates.io5 known CVEs affecting this package
Aggregated from OSV, GitHub Security Advisories, NVD, and vendor advisories. Each CVE links to its full detail page with vendor advisories, patches, fixed versions, and remediation guidance.
CVEs affecting lock_apipage 1 of 1
- CVE-2020-35910MEDIUMCVSS 5.5EG 5.5✓ Fixed in 0.4.22020-12-31
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness.
- CVE-2020-35911MEDIUMCVSS 4.7EG 4.7✓ Fixed in 0.4.22020-12-31
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness.
- CVE-2020-35912MEDIUMCVSS 4.7EG 4.7✓ Fixed in 0.4.22020-12-31
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness.
- CVE-2020-35913MEDIUMCVSS 4.7EG 4.7✓ Fixed in 0.4.22020-12-31
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.
- CVE-2020-35914MEDIUMCVSS 4.7EG 4.7✓ Fixed in 0.4.22020-12-31
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness.
Check whether lock_api is used in your infrastructure
EchelonGraph scans your cloud and SBOMs to map every package to your actual deployments. See blast radius for lock_api CVEs against the assets you own.
Start Free Scan →