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

[snyk-io-us]

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-server/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.15.0 -> 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.15.0 -> 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.15.0 -> 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

[snyk-io-us]

This upgrade from Log4j 2.15.0 to 2.25.4 includes numerous security fixes, enhancements, and some potentially breaking changes that require verification.

While the core API maintains binary compatibility, several changes could impact specific use cases. [1, 2]

Key Changes:

• Java Version: The minimum required version remains Java 8, so no environment change is required on this front. [1, 3, 7]
• Removed Modules: Several modules are no longer included in the main distribution and must be managed as separate dependencies. This is a breaking change if you use them. Notable removals include:
  • log4j-mongodb3: Users should migrate to log4j-mongodb4 or log4j-mongodb. [6]
  • log4j-kubernetes and log4j-flume-ng. [6]
• SLF4J Binding Change: Due to a break in SLF4J, Log4j now provides separate bindings for SLF4J 1.x (log4j-slf4j-impl) and SLF4J 2.x (log4j-slf4j2-impl). You must ensure your project uses the correct artifact. [1, 2]
• Configuration Hardening: Versions since 2.17.1 have introduced stricter behavior for security reasons, which may affect existing configurations:
  • Recursive lookups in properties are more restricted. [3]
  • Scripting requires explicit enablement via a system property. [3]
  • Stricter validation for configuration property names was introduced in version 2.24.0. [6]

Recommendation:
Verify your project's dependencies to see if you are using any of the removed modules. Check your logging configuration files for non-standard properties or reliance on the older, more permissive lookup behavior. If you use SLF4J, confirm you are using the correct binding artifact for your SLF4J version.

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.

[snyk-io-us]

✅ 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

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

[snyk-io]

✅ 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.

[thavelock]

✅ 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.

[snyk-io]

✅ 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

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

[snyk-io]

✅ 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.

[thavelock]

✅ 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.

[thavelock]

✅ 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.