Upgrade Log4J 2.15.0 → 2.16.0 #2022
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 upgrade provides additional mitigations for message lookup CVE Modifications: Upgrade from 2.15.0 to 2.16.0 Result: Using safer Log4J version
idelpivnitskiy
approved these changes
Dec 14, 2021
Scottmitch
approved these changes
Dec 14, 2021
|
0.41 → 51092e7 |
bondolo
added a commit
that referenced
this pull request
Dec 14, 2021
Motivation: Log4J upgrade provides additional mitigations for message lookup CVE Modifications: Upgrade from 2.15.0 to 2.16.0 Result: Using safer 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 upgrade provides additional mitigations for message lookup CVE
Modifications:
Upgrade from 2.15.0 to 2.16.0
Result:
Using safer Log4J version