CVE-2020-35859 Out of bounds access in lucet-runtime-internals

Critical 9.1 Published Updated

Guest programs can exploit mishandled sigstack allocation to read sensitive information or cause memory corruption in the lucet-runtime-internals crate.

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-35859?

CVE-2020-35859 is a critical memory corruption vulnerability in n/a, published on 31 Dec 2020. 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 lucet-runtime-internals crate before 0.5.1 for Rust. It mishandles sigstack allocation. Guest programs may be able to obtain sensitive information, or guest programs can experience memory corruption.

Weakness: CWE-787, CWE-125

Which versions are affected by CVE-2020-35859?

5 open source packages ship an affected version, including lucet-runtime-internals. It affects 1 product.

PackageAffectedFixed in
lucet-runtime-internals crates.ioAll versions0.4.3
lucet-runtime-internals crates.ioAll versions0.4.3
lucet-runtime-internals crates.ioFrom 0.0.0-00.4.3, 0.5.1
lucet-runtime-internals crates.ioFrom 0.5.00.5.1
lucet-runtime-internals crates.ioFrom 0.5.00.5.1

Products include Lucet-Runtime-Internals Project Lucet-Runtime-Internals.

How do I fix CVE-2020-35859?

Upgrade lucet-runtime-internals to a fixed version for your release line: 0.4.3 or 0.5.1.

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

Is CVE-2020-35859 being exploited?

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

Sources

Also known as GHSA-3933-wvjf-pcvc, RUSTSEC-2020-0004.

Is CVE-2020-35859 in your software?

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

Check your SBOMs for free