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

[jeremiahgrady]

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

Snyk changed the following file(s):

• todolist-goof/todolist-web-struts/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Improper Validation of Certificate with Host Mismatch SNYK-JAVA-ORGAPACHELOGGINGLOG4J-14532782	112	org.apache.logging.log4j:log4j-core: 2.7 -> 2.25.3 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:

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

[jeremiahgrady]

This is a major version upgrade that spans a significant number of releases and includes critical security hardening and environmental changes.

Key Breaking Changes:

• Java Version Requirement: The minimum required Java version has been increased. Log4j 2.7 required Java 7, but versions 2.17.2 and later require a minimum of Java 8.
• Security Hardening (Post-Log4Shell): To mitigate critical vulnerabilities, several features that were previously enabled by default are now disabled:
  • Message Lookups: Starting in version 2.15.0, lookups in log messages (e.g., ${...}) are disabled by default. Applications relying on this feature for dynamic message formatting will see a change in behavior.
  • JNDI Disabled: JNDI is disabled by default as of version 2.16.0. It must be explicitly enabled via a system property if needed.
• Legacy Configuration Bridge: As of version 2.24.0, the Log4j 1.x bridge (log4j-1.2-api) can no longer modify the Log4j Core configuration by default. If your application uses old Log4j 1.x methods like PropertyConfigurator.configure(), you must set the log4j1.compatibility=true system property or migrate to a native Log4j 2 configuration file.

Recommendation: This upgrade is essential for security. Developers must verify that their runtime environment uses Java 8 or newer. It is critical to review logging configurations and application code to ensure they do not depend on the now-disabled message lookups or JNDI features. If using the Log4j 1.x bridge for configuration, you must enable the compatibility flag or migrate your configuration.

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.

[jeremiahgrady]

⚠️ Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details
⚠️	Licenses	0	0	0	0	See details
✅	Code Security	0	0	0	0	0 issues

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