CVE-2020-36215 Data races in hashconsing

High 7.5 Published Updated

Attackers can trigger memory corruption in the Rust hashconsing crate due to missing Send/Sync bounds, potentially leading to code execution or crashes.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2020-36215?

CVE-2020-36215 is a high-severity memory corruption vulnerability in n/a, published on 22 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

An issue was discovered in the hashconsing crate before 1.1.0 for Rust. Because HConsed does not have bounds on its Send trait or Sync trait, memory corruption can occur.

Weakness: CWE-787, CWE-662

Which versions are affected by CVE-2020-36215?

3 open source packages ship an affected version, including hashconsing. It affects 1 product.

PackageAffectedFixed in
hashconsing crates.ioAll versions1.1.0
hashconsing crates.ioAll versions1.1.0
hashconsing crates.ioFrom 0.0.0-01.1.0

Products include Hashconsing Project Hashconsing.

How do I fix CVE-2020-36215?

Upgrade hashconsing to 1.1.0 or later.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2020-36215 being exploited?

There is no known exploitation of CVE-2020-36215 in the wild and no public exploit code.

Sources

Also known as GHSA-rw2c-c256-3r53, RUSTSEC-2020-0107.

Is CVE-2020-36215 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free