Fix for CVE-2024-36124 . Upgrading snappy version to 0.5. #7
Conversation
This file contains 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
|
@imjalpreet could you please help review this PR. |
imjalpreet
reviewed
Jan 16, 2025
There was a problem hiding this comment.
@namya28 thanks for the fix, LGTM.
Before we merge, could you please try to use the updated presto-hive-dwrf dependency in Presto via JitPack and see if we can get a green CI run?
6 tasks
| @@ -94,7 +94,7 @@ | |||
| <dependency> | |||
| <groupId>org.iq80.snappy</groupId> | |||
| <artifactId>snappy</artifactId> | |||
| <version>0.2</version> | |||
| <version>0.5</version> | |||
There was a problem hiding this comment.
@namya28 I see 0.5 also has CVEs? https://mvnrepository.com/artifact/org.iq80.snappy/snappy/0.5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is for upgrading the snappy version from 0.2 to 0.5 as the version 0.2 has a security vulnerability. Upgrading this version to 0.5 fixes the CVE-2024-36124.