at.yawk.lz4:lz4-java vulnerabilities
Java bindings and pure Java implementations of LZ4 and XXHash
- Registry
- Maven
- Latest
- 1.14.1
- License
- Apache License, Version 2.0
8 known advisories
The latest version, 1.14.1, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=at.yawk.lz4:lz4-java -DdepVersion=1.14.1 -DforceVersion=trueIs your project on an affected at.yawk.lz4:lz4-java?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for at.yawk.lz4:lz4-java
yawkat LZ4 Java: Native library extraction to a shared temporary directory is vulnerable to file replacement by another local user
- Affected
- <1.11.4
- Fixed in
- 1.11.4
yawkat LZ4 Java: LZ4BlockInputStream with stopOnEmptyBlock=false recurses once per empty block, causing StackOverflowError
- Affected
- <1.11.4
- Fixed in
- 1.11.4
yawkat LZ4 Java: LZ4FrameInputStream reallocates block buffers for every frame, allowing CPU and GC amplification from small inputs
- Affected
- <1.11.4
- Fixed in
- 1.11.4
yawkat LZ4 Java: LZ4BlockInputStream allocates an unvalidated compressed length from the stream header
- Affected
- <1.11.2
- Fixed in
- 1.11.2
yawkat LZ4 Java: LZ4DecompressorWithLength allocates the unvalidated size from the 4-byte length header, so a 5-byte input triggers a 1 GiB allocation and OutOfMemoryError
- Affected
- <1.11.2
- Fixed in
- 1.11.2
LZ4 Java: Native XXHash implementations can crash the JVM when passed invalid byte array ranges
- Affected
- <1.11.1
- Fixed in
- 1.11.1
yawkat LZ4 Java has a possible information leak in Java safe decompressor
- Affected
- <1.10.1
- Fixed in
- 1.10.1
LZ4 Java Compression has Out-of-bounds memory operations which can cause DoS
- Affected
- <1.8.1
- Fixed in
- 1.8.1
Is your at.yawk.lz4:lz4-java version vulnerable?
- at.yawk.lz4:lz4-java 1.14No known advisories in 1.14.1
- at.yawk.lz4:lz4-java 1.13No known advisories in 1.13.0
- at.yawk.lz4:lz4-java 1.12No known advisories in 1.12.1
- at.yawk.lz4:lz4-java 1.11No known advisories in 1.11.4
- at.yawk.lz4:lz4-java 1.106 advisories in 1.10.4
- at.yawk.lz4:lz4-java 1.97 advisories in 1.9.0
Which of your client projects still run an old at.yawk.lz4:lz4-java?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.