CVE-2021-45105: Bumping Log4j to 2.17.0 on elasticsearch5, ignite, and voltdb #1583
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
gkorland
approved these changes
Dec 21, 2021
elukey
added a commit
to elukey/bigtop
that referenced
this pull request
Dec 28, 2021
At the time of writing upstream didn't release any official fix, but brianfrankcooper/YCSB#1583 seems taking care of it. Credits for the upstream fix: Filipe Oliveira <[email protected]>
elukey
added a commit
to apache/bigtop
that referenced
this pull request
Dec 31, 2021
At the time of writing upstream didn't release any official fix, but brianfrankcooper/YCSB#1583 seems taking care of it. Credits for the upstream fix: Filipe Oliveira <[email protected]>
|
@filipecosta90 Thanks a lot for the patch, it has been included in Apache Bigtop's ycsb package :) |
elukey
added a commit
to elukey/bigtop
that referenced
this pull request
Dec 31, 2021
At the time of writing upstream didn't release any official fix for the lo4j CVEs, but brianfrankcooper/YCSB#1583 seems taking care of it. Credits for the upstream fix: Filipe Oliveira <[email protected]> This change also bumps ycsb to its latest upstream, to allow the log4j patch to be applied cleanly.
elukey
added a commit
to elukey/bigtop
that referenced
this pull request
Dec 31, 2021
At the time of writing upstream didn't release any official fix for the lo4j CVEs, but brianfrankcooper/YCSB#1583 seems taking care of it. Credits for the upstream fix: Filipe Oliveira <[email protected]> This change also bumps ycsb to its latest upstream, to allow the log4j patch to be applied cleanly.
elukey
added a commit
to apache/bigtop
that referenced
this pull request
Jan 8, 2022
At the time of writing upstream didn't release any official fix for the lo4j CVEs, but brianfrankcooper/YCSB#1583 seems taking care of it. Credits for the upstream fix: Filipe Oliveira <[email protected]> This change also bumps ycsb to its latest upstream, to allow the log4j patch to be applied cleanly.
iwasakims
pushed a commit
to apache/bigtop
that referenced
this pull request
Jan 11, 2022
At the time of writing upstream didn't release any official fix, but brianfrankcooper/YCSB#1583 seems taking care of it. Credits for the upstream fix: Filipe Oliveira <[email protected]> (cherry picked from commit 265e891)
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.
Following up on Security Vulnerability CVE-2021-45105