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.
Product
crates.io parc vulnerabilities
2 published CVES affecting crates.io parc, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 2
- Critical
- 0
- High
- 2
- Medium
- 0
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest crates.io parc CVEs
Newest publication first
-
HighCVSS 8.1
-
CVE-2020-36454 Data races in parc
PublishedHighCVSS 8.1 EPSS 0.83%An issue was discovered in the parc crate through 2020-11-14 for Rust. LockWeak<T> has an unconditional implementation of Send without trait bounds on T.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.