Rust advisories / parc
Vulnerability HighRUSTSEC-2020-0134 · parc
RUSTSEC-2020-0134: `LockWeak<T>` allows to create data race to `T`.
Short answerA security vulnerability in the parc crate: `LockWeak<T>` allows to create data race to `T`.. High severity (CVSS 8.1). No fixed version: replace the crate or remove the affected code path.
| Crate | parc |
|---|---|
| Type | Vulnerability (memory-corruption, thread-safety) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | High, CVSS 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | 2020-11-14 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36454, GHSA-29v7-3v4c-gf38, GHSA-xwxc-j97j-84gf |
What to do
- Find who pulls it in:
cargo tree -i parc. - Avoid the affected API, or replace the crate.
Details from the advisory
In the affected versions of this crate, LockWeak<T> unconditionally implemented Send with no trait bounds on T. LockWeak<T> doesn't own T and only provides &T.
This allows concurrent access to a non-Sync T, which can cause undefined behavior like data races.
References
- Package: crates.io/crates/parc
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0134.html
- Web: github.com/hyyking/rustracts/pull/6
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?