Lucene search
+L

4 matches found

RustSec
RustSec
•added 2026/10/16 12:00 p.m.•8 views

Uninitialized memory exposed by `write::Decoder` on a corrupt legacy frame

From 0.4.22 to 0.7.x, the writer behind zstd::stream::write::Decoder set its output buffer's length to its full capacity before each decompression call, then to the position the call reported, and only checked for an error afterwards. When decompression fails inside a legacy zstd v0.4 to v0.7...

6.1AI score
SaveExploits0Affected Software1
RustSec
RustSec
•added 2026/10/16 12:00 p.m.•9 views

Uninitialized memory exposed when streaming decompression of a legacy frame fails

When decompression fails inside a legacy zstd v0.4 to v0.7 frame, the bundled zstd library reports the output buffer as fully written although nothing was written. DCtx::decompressstream committed that position even on error, and for a Vec destination this extended the vector's length over...

5.9AI score
SaveExploits0Affected Software1
Positive Technologies
Positive Technologies
•added 2026/10/16 12:00 a.m.•3 views

PT-2026-125062

When decompression fails inside a legacy zstd v0.4 to v0.7 frame, the bundled zstd library reports the output buffer as fully written although nothing was written. DCtx::decompress stream committed that position even on error, and for a Vec destination this extended the vector's length over...

5.9AI score
SaveExploits0References5
Positive Technologies
Positive Technologies
•added 2026/10/16 12:00 a.m.•3 views

PT-2026-125051

From 0.4.22 to 0.7.x, the writer behind zstd::stream::write::Decoder set its output buffer's length to its full capacity before each decompression call, then to the position the call reported, and only checked for an error afterwards. When decompression fails inside a legacy zstd v0.4 to v0.7...

6.1AI score
SaveExploits0References5
Rows per page
Query Builder