Update to log4j 2.15.0 to fix security issue #11907
Merged
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
Motivation: log4j 2.15.0 was released to fix a 0-day security issue. While the log4j dependency is fully optional we should still upgrade. See https://www.lunasec.io/docs/blog/log4j-zero-day/ Modifications: Upgrade to 2.15.0 Result: Use non-affected log4j version
|
See #11905 |
chrisvest
approved these changes
Dec 10, 2021
This was referenced Dec 14, 2021
laosijikaichele
pushed a commit
to laosijikaichele/netty
that referenced
this pull request
Dec 16, 2021
Motivation: log4j 2.15.0 was released to fix a 0-day security issue. While the log4j dependency is fully optional we should still upgrade. See https://www.lunasec.io/docs/blog/log4j-zero-day/ Modifications: Upgrade to 2.15.0 Result: Use non-affected log4j version
laosijikaichele
pushed a commit
to laosijikaichele/netty
that referenced
this pull request
Dec 16, 2021
Motivation: log4j 2.15.0 was released to fix a 0-day security issue. While the log4j dependency is fully optional we should still upgrade. See https://www.lunasec.io/docs/blog/log4j-zero-day/ Modifications: Upgrade to 2.15.0 Result: Use non-affected log4j version
10brothers
pushed a commit
to 10brothers/netty
that referenced
this pull request
Jan 20, 2022
Motivation: log4j 2.15.0 was released to fix a 0-day security issue. While the log4j dependency is fully optional we should still upgrade. See https://www.lunasec.io/docs/blog/log4j-zero-day/ Modifications: Upgrade to 2.15.0 Result: Use non-affected log4j version
raidyue
pushed a commit
to raidyue/netty
that referenced
this pull request
Jul 8, 2022
Motivation: log4j 2.15.0 was released to fix a 0-day security issue. While the log4j dependency is fully optional we should still upgrade. See https://www.lunasec.io/docs/blog/log4j-zero-day/ Modifications: Upgrade to 2.15.0 Result: Use non-affected log4j version
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.
Motivation:
log4j 2.15.0 was released to fix a 0-day security issue. While the log4j dependency is fully optional we should still upgrade
Modifications:
Upgrade to 2.15.0
Result:
Use non-affected log4j version