lz4-java: New project submission #14353
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
yawkat is integrating a new project: |
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.
Contributor
Author
|
CLA passes now, the first version of this PR had the wrong e-mail address. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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, such as hadoop, spark, kafka and netty.
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 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.