Rust advisories / lucet-runtime-internals
Vulnerability CriticalRUSTSEC-2020-0004 · lucet-runtime-internals
RUSTSEC-2020-0004: sigstack allocation bug can cause memory corruption or leak
Short answerA security vulnerability in the lucet-runtime-internals crate: sigstack allocation bug can cause memory corruption or leak. Critical severity (CVSS 9.1). Fixed in 0.4.3, 0.5.1: update to a fixed version.
| Crate | lucet-runtime-internals |
|---|---|
| Type | Vulnerability (memory-corruption, memory-exposure) |
| Affected versions | Before 0.4.3; from 0.5.0 before 0.5.1. |
| Fixed in | 0.4.3, 0.5.1 |
| Severity | Critical, CVSS 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
| Published | 2020-01-24 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-35859, GHSA-3933-wvjf-pcvc |
What to do
- See which version you have:
cargo tree -i lucet-runtime-internals(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p lucet-runtime-internals. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplelucet-runtime-internals = "0.5.1") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
An embedding using affected versions of lucet-runtime configured to use non-default Wasm globals sizes of more than 4KiB, or compiled in debug mode without optimizations, could leak data from the signal handler stack to guest programs. This can potentially cause data from the embedding host to leak to guest programs or cause corruption of guest program memory.
This flaw was resolved by correcting the sigstack allocation logic.
References
- Package: crates.io/crates/lucet-runtime-internals
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0004.html
- Web: github.com/bytecodealliance/lucet/pull/401
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?