Use-after-free of a dictionary after a one-shot call on a context with an open stream
- 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 python-zstandard Python bindings for the Zstandard compression library are affected when an application reuses one context for both streaming and one-shot calls without a reset in between. This can cause decompressed output to contain freed heap memory and can corrupt compressed output.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
The one-shot `DCtx` and `CCtx` methods assumed the C library resets the context, but it leaves an open stream as it is. When a stream was left unfinished on a context, a one-shot call such as `decompress_using_dict` could leave the context pointing at the dictionary borrowed for that call, and the next streaming call resumed the stream against it after it was freed: decompressed output then contained freed heap memory. On the compression side, the stream resumed against the one-shot call's buffers. This requires an application to use one context for both streaming and one-shot calls without a reset in between. The flaw was corrected by resetting the session after one-shot calls whenever a stream may be open.
Timeline
- Advisory published
- Record last updated
Affected versions
- zstd-safecrates.io
From 3.0.1 · fixed in 8.2.0