Description
zstd-jni before 1.5.7-14 performs 32-bit signed bounds checks on three direct-ByteBuffer frame-size native methods, allowing out-of-bounds memory reads via negative or overflowing offsets. Attackers can supply negative offset values near Integer.MIN_VALUE to read unmapped memory, causing JVM termination or extracting arbitrary frame size data from unintended memory locations.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
luben zstd-jni
Default version status: unaffected
1.1.1 to < 1.5.7-14affected
pkg:maven/com.github.luben/zstd-jniReferences
- https://github.com/luben/zstd-jni/security/advisories/GHSA-jfr6-9xqw-2g2q ↗
- https://github.com/luben/zstd-jni/commit/d7a1c99322d5e1fc71932e722c0b5bb2fc525d3f ↗
- https://github.com/luben/zstd-jni/blob/v1.5.7-13/src/main/native/jni_zstd.c ↗
- https://github.com/luben/zstd-jni/blob/v1.5.7-13/src/main/java/com/github/luben/zstd/Zstd.java ↗
- https://github.com/luben/zstd-jni/releases/tag/v1.5.7-14 ↗
- https://github.com/luben/zstd-jni/commit/46dcb2a54c8b8f2ce2cad7187a7513f509c533ac ↗
- https://github.com/luben/zstd-jni ↗
- https://www.vulncheck.com/advisories/zstd-jni-1.1.1-through-1.5.7-13-out-of-bounds-read-via-direct-bytebuffer-frame-size-methods ↗