GHSA-x3f4-45xf-rjm7 json
`ruzstd` uninit and out-of-bounds memory reads
published last yr. modified 2mo ago also RUSTSEC-2024-0400
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Affected versions of `ruzstd` miscalculate the length of the allocated and init section of its internal `RingBuffer`, leading to uninitialized or out-of-bounds reads in `copy_bytes_overshooting` of up to 15 bytes.
This may result in up to 15 bytes of memory contents being written into the decoded data when decompressing a crafted archive. This may occur multiple times per archive.
Patch / fix
Is GHSA-x3f4-45xf-rjm7 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | ruzstd | >=0.7.0, <0.7.3 |
0.7.3 |
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/KillingSpark/zstd-rs/pull/76
web
-
github.com
/KillingSpark/zstd-rs/issues/75
web, report
-
github.com
/KillingSpark/zstd-rs
package
-
rustsec.org
/advisories/RUSTSEC-2024-0400.html
web, advisory
-
crates.io
/crates/ruzstd
package
Sources
- GitHub Advisory GHSA-x3f4-45xf-rjm7
- OSV RUSTSEC-2024-0400
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.