HADOOP-19747. Switch to at.yawk.lz4:lz4-java:1.9.0 due to CVE-2025-12183#8116
Merged
steveloughran merged 1 commit intoapache:trunkfrom Dec 4, 2025
Merged
HADOOP-19747. Switch to at.yawk.lz4:lz4-java:1.9.0 due to CVE-2025-12183#8116steveloughran merged 1 commit intoapache:trunkfrom
steveloughran merged 1 commit intoapache:trunkfrom
Conversation
steveloughran
approved these changes
Dec 2, 2025
Contributor
steveloughran
left a comment
steveloughran
left a comment
There was a problem hiding this comment.
+1
In the long term, it is recommended to switch to .safeDecompressor(), which is not vulnerable and provides better performance (despite the name).
Member
Author
|
@steveloughran I think Hadoop uses safe decompressor already |
slfan1989
approved these changes
Dec 3, 2025
steveloughran
pushed a commit
that referenced
this pull request
Dec 4, 2025
(#8116) The hadoop decompressor org.apache.hadoop.io.compress.lz4.Lz4Compressor instantiated a compressor via a call to LZ4Factory.fastestInstance().safeDecompressor() and so is not directly vulnerable to CVE-2025-12183. see https://sites.google.com/sonatype.com/vulnerabilities/cve-2025-12183 Contributed by PJ Fanning
Member
Author
|
@steveloughran do you think it is ok to backport this to the 3.4 branch? |
Member
|
Just FYI, lz4 is famous for its ultra-fast speed, the upgrade is not free, my test shows it has perf impact |
steveloughran
pushed a commit
that referenced
this pull request
Jan 5, 2026
(#8116) The hadoop decompressor org.apache.hadoop.io.compress.lz4.Lz4Compressor instantiated a compressor via a call to LZ4Factory.fastestInstance().safeDecompressor() and so is not directly vulnerable to CVE-2025-12183. see https://sites.google.com/sonatype.com/vulnerabilities/cve-2025-12183 Contributed by PJ Fanning
asf-gitbox-commits
pushed a commit
that referenced
this pull request
Jan 5, 2026
(#8116) The hadoop decompressor org.apache.hadoop.io.compress.lz4.Lz4Compressor instantiated a compressor via a call to LZ4Factory.fastestInstance().safeDecompressor() and so is not directly vulnerable to CVE-2025-12183. see https://sites.google.com/sonatype.com/vulnerabilities/cve-2025-12183 Contributed by PJ Fanning
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description of PR
HADOOP-19747
How was this patch tested?
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?