CVE-2020-35859 json
Out of bounds access in lucet-runtime-internals
published 6y ago modified 4mo ago also GHSA-3933-wvjf-pcvc , RUSTSEC-2020-0004 , EUVD-2021-1537
- cvss
- 9.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io lucet-runtime-internals 0.4.3, 0.5.1
- lucet-runtime-internals_project lucet-runtime-internals 0.5.1
- github.com/bytecodealliance/lucet#401 pull request
- rustsec.org/advisories/RUSTSEC-2020-0004.html advisory
Is CVE-2020-35859 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.52% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:N/A:P |
| OSV | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | lucet-runtime-internals | <0.4.3 >=0.5.0, <0.5.1 >=0.0.0-0, <0.4.3 |
0.4.3 0.5.1 |
Classification
References
-
rustsec.org
/advisories/RUSTSEC-2020-0004.html
web, patch, third-party-advisory, advisory
-
github.com
/bytecodealliance/lucet/pull/401
web
-
nvd.nist.gov
/vuln/detail/CVE-2020-35859
advisory
-
github.com
/fastly/lucet
package
-
crates.io
/crates/lucet-runtime-internals
package
Sources
- CVE List CVE-2020-35859
- GitHub Advisory GHSA-3933-wvjf-pcvc
- NVD CVE-2020-35859
- OSV RUSTSEC-2020-0004
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.