yawkat LZ4 Java has a possible information leak in Java safe decompressor
yawkat lz4-java
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| at.yawk.lz4:lz4-java Maven |
|
|
| org.lz4:lz4-java Maven |
| No fix yet |
| org.lz4:lz4-pure-java Maven |
|
yawkat lz4-java
| Product | Affected | Fixed in |
|---|---|---|
| at.yawk.lz4:lz4-java Maven |
|
|
| org.lz4:lz4-java Maven |
| No fix yet |
| org.lz4:lz4-pure-java Maven |
|
| No fix yet |
| net.jpountz.lz4:lz4 Maven |
| No fix yet |
yawkat LZ4 Java provides LZ4 compression for Java. Insufficient clearing of the output buffer in Java-based decompressor implementations in lz4-java 1.10.0 and earlier allows remote attackers to read previous buffer contents via crafted compressed input. In applications where the output buffer is reused without being cleared, this may lead to disclosure of sensitive data. JNI-based implementations are not affected. This vulnerability is fixed in 1.10.1.
From the CVE record · GitHub_M
Java-based decompressors in lz4-java may leave previous data in an output buffer. A remote attacker can use crafted compressed input to read that data when an application reuses the buffer without clearing it, potentially exposing sensitive information. JNI-based implementations are not affected; authentication and user-interaction requirements are not specified.
Check applications using Maven at.yawk.lz4:lz4-java before 1.10.1, or org.lz4:lz4-java, org.lz4:lz4-pure-java, or net.jpountz.lz4:lz4 at version 1.8.1 or earlier.