| Title | luben zstd-jni 1.5.7-13 Missing Bounds Check |
|---|
| Description | Right after confirming the broken bounds check in ZstdDictCompress's constructor, I checked the decompression-side sibling ZstdDictDecompress(byte[] dict, int offset, int length) — it has the same shape of bug but is worse: there's no validation at all, not even the partial check its compression counterpart has. I confirmed this with a real crash. No check on offset, length, or their relationship to dict.length whatsoever. The native function forwards them straight into ZSTD_createDDict. |
|---|
| Source | ⚠️ https://github.com/luben/zstd-jni/issues/405 |
|---|
| User | Yu Bao from PayPal Cyber Security Team (UID 99838) |
|---|
| Submission | 08/13/2026 07:28 (1 month ago) |
|---|
| Moderation | 09/14/2026 07:37 (1 month later) |
|---|
| Status | Duplicate |
|---|
| VulDB entry | 403174 [luben zstd-jni up to 1.5.7-13 Dictionary Decompression ZstdDictDecompress constructor offset/length out-of-bounds] |
|---|
| Points | 0 |
|---|