CVE-2020-35924 Data races in try-mutex

Medium 5.5 Published Updated

The try-mutex crate allows sending non-Send types across threads, potentially causing memory corruption and crashes in Rust applications.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2020-35924?

CVE-2020-35924 is a medium-severity memory corruption vulnerability in n/a, published on 31 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

An issue was discovered in the try-mutex crate before 0.3.0 for Rust. TryMutex<T> allows cross-thread sending of a non-Send type.

Weakness: CWE-787

Which versions are affected by CVE-2020-35924?

3 open source packages ship an affected version, including try-mutex. It affects 1 product.

PackageAffectedFixed in
try-mutex crates.ioAll versions0.3.0
try-mutex crates.ioAll versions0.3.0
try-mutex crates.ioFrom 0.0.0-00.3.0

Products include Try-Mutex Project Try-Mutex.

How do I fix CVE-2020-35924?

Upgrade try-mutex to 0.3.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-35924 being exploited?

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

Sources

Also known as GHSA-64j8-7gp2-xjx5, RUSTSEC-2020-0087.

Is CVE-2020-35924 in your software?

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

Check your SBOMs for free