Skip to content

[Snyk] Security upgrade org.apache.logging.log4j:log4j-core from 2.14.1 to 2.25.3#18

Open
DariusZdroba wants to merge 1 commit intomainfrom
snyk-fix-a83773574d6aceb688a32fa791ce573e
Open

[Snyk] Security upgrade org.apache.logging.log4j:log4j-core from 2.14.1 to 2.25.3#18
DariusZdroba wants to merge 1 commit intomainfrom
snyk-fix-a83773574d6aceb688a32fa791ce573e

Conversation

@DariusZdroba
Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • log4shell-goof/log4shell-client/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
medium severity Improper Validation of Certificate with Host Mismatch
SNYK-JAVA-ORGAPACHELOGGINGLOG4J-14532782
  113   org.apache.logging.log4j:log4j-core:
2.14.1 -> 2.25.3
No Known Exploit

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@DariusZdroba
Copy link
Copy Markdown
Owner Author

Merge Risk: High

This upgrade spans a significant number of versions and introduces several breaking changes, primarily from version 2.24.0 onwards. This is in addition to the critical security fixes related to Log4Shell (CVE-2021-44228) introduced since version 2.15.0.

Breaking Changes:

  • JMX Disabled: As of version 2.24.0, JMX is disabled by default and must be explicitly re-enabled. [1]
  • Log Format Change: The timeMillis attribute in XML, JSON, and YAML layouts has been replaced with an Instant object, which will break downstream log parsing. [1]
  • Legacy Configuration: Programmatic configuration using Log4j v1 or java.util.logging (JUL) bridge APIs is now disabled by default. [7, 9]
  • Module Removal: The log4j-kubernetes, log4j-flume-ng, and log4j-mongodb3 modules have been removed and must be added as separate dependencies if used. [7]

Recommendation: Review configurations for JMX, legacy API calls, and update any log processing pipelines that rely on the old timestamp format. Add explicit dependencies for removed modules.

Source: Apache Log4j Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants