`Seekable` reads a NULL or out-of-bounds seek table
- 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 `Seekable` component of the zstd seekable-format library (used through its Rust bindings) can read a NULL or out-of-bounds seek table, which can crash the program or return data from a previously loaded buffer after a failed re-initialization. Applications that use seekable zstd decompression to access compressed data by offset or frame index are affected.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
`Seekable` did not record whether it was initialized. On a fresh `Seekable`, or one whose `init_buff()` failed, `decompress`, `offset_to_frame_index` and `frame_decompressed_size` made the C library read a NULL seek table. After a failed re-initialization, `decompress` returned data from the refused buffer using the previous seek table. Separately, `frame_decompressed_size(num_frames())`, on `Seekable` and `SeekTable`, read one entry past the end of the seek table. The flaw was corrected by refusing to use a `Seekable` until an initialization succeeded, and by checking the frame index.
Timeline
- Advisory published
- Record last updated
Affected versions
- zstd-safecrates.io
From 7.2.2 · fixed in 8.2.0