Bump: log4j to 2.16.0 #1845
Merged
Bump: log4j to 2.16.0 #1845
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
princeyesuraj
requested review from
maciejwalkowiak,
marandaneto and
romtsn
as code owners
|
@princeyesuraj thanks for doing that, please add a changelog entry |
Added the changelog |
marandaneto
approved these changes
Dec 15, 2021
maciejwalkowiak
pushed a commit
that referenced
this pull request
Jan 5, 2022
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.
馃摐 Description
Bump log4j-api,log4j-core from 2.15.0 to 2.16.0
馃挕 Motivation and Context
CVE 2021-45046
Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attack.
馃挌 How did you test it?
馃摑 Checklist
馃敭 Next steps