Register for the AI for Security Summit: Join Figma, Perplexity & Wiz
Vulnerability DatabaseRUSTSEC-2020-0134

RUSTSEC-2020-0134
Rust vulnerability analysis and mitigation

Overview

An issue was discovered in the parc crate through 2020-11-14 for Rust, identified as RUSTSEC-2020-0134 (CVE-2020-36454). The vulnerability involves the LockWeak implementation, which had an unconditional implementation of Send without trait bounds on T, potentially leading to unsafe concurrent access (RustSec Advisory).

Technical details

The vulnerability stems from the LockWeak structure having an unsafe implementation of the Send trait without proper trait bounds on the generic type T. This implementation allowed the creation of data races by enclosing a non-Sync type data to ParentArc and accessing the enclosed data from multiple threads via ChildArc. The issue has been assigned a CVSS v3.1 base score of 8.1 (HIGH) with the vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (NVD Database).

Impact

The vulnerability could lead to undefined behavior in safe Rust code. When exploited, it could result in data races, memory leaks, or program crashes. In proof-of-concept demonstrations, the issue could manifest in various ways including program panics, memory leaks with strong_count > 1, or premature dropping of Rc while references were still active (GitHub PR).

Exploitability

The vulnerability can be triggered using safe Rust code, making it particularly concerning. A proof of concept demonstrated that the issue could be exploited by creating multiple threads accessing non-Sync type data concurrently, leading to undefined behavior particularly noticeable in Debug mode (GitHub PR).

Mitigation and workarounds

The issue was fixed by adding a Sync bound to the Send implementation of LockWeak, preventing concurrent access to the underlying data from multiple threads. The fix ensures that only types that implement both Send and Sync can be safely shared between threads (GitHub PR).

Community reactions

The vulnerability was discovered by the Rust group at Georgia Tech (@sslab-gatech) during a scan of crates.io. The issue was subsequently included in the RustSec advisory database and is now detected by security tools such as cargo-audit and cargo-deny (GitHub PR).

Additional resources


SourceThis report was generated using AI

Related Rust vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-68537HIGH7.5
  • Rust logoRust
  • fulgur
NoYesSep 17, 2026
CVE-2026-68523HIGH7.5
  • Rust logoRust
  • fulgur
NoYesSep 17, 2026
RUSTSEC-2026-0289NONEN/A
  • Rust logoRust
  • pqc_kyber
NoNoSep 17, 2026
RUSTSEC-2026-0287NONEN/A
  • Rust logoRust
  • cosmian_kyber
NoNoSep 17, 2026
RUSTSEC-2026-0286NONEN/A
  • Rust logoRust
  • cryptoki
NoYesSep 16, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management