Skip to content

Commit 149f6c9

Browse files
committed
lz4-java: New project submission
I would like to submit my lz4-java fork for OSS-Fuzz. lz4-java itself has an OSSF criticality score of only 0.56. However it is a [dependency of some important OSS infrastructure](https://mvnrepository.com/artifact/org.lz4/lz4-java/usages), such as hadoop, spark, kafka and netty. [CVE-2025-12183](https://sites.google.com/sonatype.com/vulnerabilities/cve-2025-12183) was discovered using OSS-Fuzz, but the path was very indirect: A Micronaut fuzz test was exercising a netty class (micronaut depends on netty) which in turn found the bug in lz4-java. Additional local fuzzing of lz4-java found numerous further subtle security issues that were also addressed in the CVE. The project governance is problematic. The original maintainer was not reachable, and the lz4 organization decided to close the project. My fork is linked [in the README](https://github.com/lz4/lz4-java) as the community continuation of the project. That is why I am submitting my fork, not the original. The combination of high impact (many people decompress untrusted data), poor security hardening, and demonstrated previous discoveries make an OSS-Fuzz integration sensible, even if circumstances are unusual. I am not looking for integration awards.
1 parent c74d767 commit 149f6c9

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

projects/lz4-java/project.yaml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
homepage: "https://github.com/yawkat/lz4-java"
2+
main_repo: "https://github.com/yawkat/lz4-java"
3+
language: java
4+
primary_contact: "[email protected]"
5+
auto_ccs:
6+

0 commit comments

Comments
 (0)