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

[philvarner-snyk]

Snyk has created this PR to fix 3 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
	Improper Validation of Certificate with Host Mismatch SNYK-JAVA-ORGAPACHELOGGINGLOG4J-15967727	113	org.apache.logging.log4j:log4j-core: 2.14.1 -> 2.25.4 No Path Found No Known Exploit
	Improper Encoding or Escaping of Output SNYK-JAVA-ORGAPACHELOGGINGLOG4J-15967769	67	org.apache.logging.log4j:log4j-core: 2.14.1 -> 2.25.4 No Path Found No Known Exploit
	Improper Encoding or Escaping of Output SNYK-JAVA-ORGAPACHELOGGINGLOG4J-15967804	67	org.apache.logging.log4j:log4j-core: 2.14.1 -> 2.25.4 No Path Found No Known Exploit

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Improper Encoding or Escaping of Output

[philvarner-snyk]

This upgrade spans multiple significant releases, including the critical security updates that addressed the Log4Shell vulnerability (CVE-2021-44228). It introduces several breaking changes and important behavioral modifications that require verification.

Key Breaking Changes:

• Message Lookups Disabled by Default (v2.15.0+): To mitigate the Log4Shell vulnerability, message lookups (${...}) are no longer enabled by default. If your application relied on this feature, you must explicitly enable it in your pattern layout (e.g., %m{lookups}). However, this is strongly discouraged for security reasons.

• JNDI Hardening (v2.17.0+): JNDI is now disabled by default. Enabling JNDI features requires setting specific system properties (e.g., log4j2.enableJndiLookup). The generic log4j2.enableJndi property has been removed.

• Removed Modules (v2.24.0+): The log4j-mongodb3, log4j-flume-ng, and log4j-kubernetes modules have been removed from the main project and now have independent release cycles. If you use these, you must update your project dependencies to include them directly.

• Java Version: The minimum requirement of Java 8 is unchanged between version 2.14.1 and 2.25.4.

Recommendation:

Due to the security-driven breaking changes, you must carefully review your logging configurations (log4j2.xml, etc.). Verify that your logging patterns and any use of JNDI are still functioning as expected. If you use any of the removed modules, update your build to include the new artifacts.

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

[philvarner-snyk]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.