CVE-2020-35912

unknown
Published 2020-11-08 ยท Modified 2024-03-15
CVSS v3
โ€”
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
โ€”

Description

An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness.

Predictions

Exploit likelihood
20%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

debian Debian Mixed 5 releases
VersionStatusFixed in
trixie Fixed 0.4.5-1
sid Fixed 0.4.5-1
forky Fixed 0.4.5-1
bullseye Affected โ€”
bookworm Fixed 0.4.5-1

Package impact

EcosystemPackageVulnerableFixed
rust crates.iolock_api
rust crates.iolock_api<0.4.20.4.2
rust crates.iolock_api>=0.0.0-0,<0.4.20.4.2

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.