-
-
Notifications
You must be signed in to change notification settings - Fork 487
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump log4j-core and log4j-api from 2.15.0 to 2.16.0 #6079
Merged
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
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. As far as we know GeoNetwork doesn't use any of these pattern layouts but anyway this commit updates log4j to 2.16.0 that fixes the new CVE-2021-45046 disabling access to JNDI by default and removing the message lookups feature.
juanluisrp
added
dependencies
Pull requests that update a dependency file
backport 3.10.x
backport 3.12.x
labels
Dec 15, 2021
josegar74
approved these changes
Dec 15, 2021
josegar74
pushed a commit
that referenced
this pull request
Dec 15, 2021
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. As far as we know GeoNetwork doesn't use any of these pattern layouts but anyway this commit updates log4j to 2.16.0 that fixes the new CVE-2021-45046 disabling access to JNDI by default and removing the message lookups feature.
josegar74
pushed a commit
that referenced
this pull request
Dec 15, 2021
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. As far as we know GeoNetwork doesn't use any of these pattern layouts but anyway this commit updates log4j to 2.16.0 that fixes the new CVE-2021-45046 disabling access to JNDI by default and removing the message lookups feature.
josegar74
pushed a commit
that referenced
this pull request
Dec 17, 2021
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. As far as we know GeoNetwork doesn't use any of these pattern layouts but anyway this commit updates log4j to 2.16.0 that fixes the new CVE-2021-45046 disabling access to JNDI by default and removing the message lookups feature.
josegar74
pushed a commit
that referenced
this pull request
Dec 17, 2021
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. As far as we know GeoNetwork doesn't use any of these pattern layouts but anyway this commit updates log4j to 2.16.0 that fixes the new CVE-2021-45046 disabling access to JNDI by default and removing the message lookups feature.
josegar74
pushed a commit
that referenced
this pull request
Dec 17, 2021
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. As far as we know GeoNetwork doesn't use any of these pattern layouts but anyway this commit updates log4j to 2.16.0 that fixes the new CVE-2021-45046 disabling access to JNDI by default and removing the message lookups feature.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
It was found that the fix to address CVE-2021-44228 in Apache Log4j
2.15.0
was incompletein certain non-default configurations.
As far as we know GeoNetwork doesn't use any of these pattern layouts but anyway this
commit updates log4j to
2.16.0
that fixes the new CVE-2021-45046 disabling access toJNDI by default and removing the message lookups feature.