`OutBuffer::around_pos` exposes uninitialized memory
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 8.2.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The affected software is the Rust `OutBuffer` component used for streaming data processing, where `OutBuffer::around_pos` could be called with a position beyond the buffer's initialized length. The flaw could let safe code read leftover, uninitialized heap memory, potentially exposing sensitive data from earlier program activity.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
`OutBuffer::around_pos` accepted a position past the initialized length of a `Vec<u8>`. The next streaming call then marked everything before the position as initialized, so safe code could read stale heap memory between the vector's previous length and that position. The flaw was corrected by zero-filling that gap.
Timeline
- Advisory published
- Record last updated
Affected versions
- zstd-safecrates.io
From 4.0.0 · fixed in 8.2.0