log4j 2.15.0 - fixes security vulnerability CVE-2021-44228 (#285) #286
Conversation
This file contains hidden or 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
|
@droobertzka we'll fasttrack this review for obvious reasons! Thank you for the contribution. |
diegov
approved these changes
Dec 14, 2021
|
Awesome. Thanks for the quick review and merge! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 of the change
Updates log4j2 to remediate security vulnerability CVE-2021-44228 in <2.15.0
Type of change
Related issues
Checklists
Development
As this is only a minor dependency update, it would not have affected any linting or tests. If anyone has this project set up to verify them, please do.
Code review