[SCA] Security upgrade @org.apache.logging.log4j:log4j-core from 2.7 to 2.25.4

[gwnlng]

This is a PR from Snyk, initiated by the Security team, to fix 9 vulnerabilities in the dependencies of this project.

Snyk changed the following file(s):

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

Important

• This PR was automatically generated by our security tool to help you fix known vulnerabilities in your project's third-party libraries more efficiently. However, there is a possibility that these changes could introduce functional regressions or breakages. Please ensure you test this PR thoroughly before merging.
• If you have any questions or concerns, please seek support in the #sca-support Slack channel.

References:

1. Latest project report in Snyk
2. How to access Snyk via SSO?
3. Snyk knowledge base

[gwnlng]

This is a significant upgrade from version 2.7 to 2.25.4, which introduces several breaking changes and requires a Java runtime update.

Key Changes:

• Java Version Requirement: The minimum required Java version has been increased. Log4j 2.7 required Java 7, while versions 2.12.1 and later require Java 8. Your environment must be running on Java 8 or newer.

• Configuration Changes:

  • Timestamp Format: The XML, JSON, and YAML formats no longer use the timeMillis attribute as of version 2.11.0. They now use an Instant element with epochSecond and nanoOfSecond attributes.
  • Property Names: As of version 2.24.0, the configuration properties subsystem is stricter and only accepts official or normalized property names.
  • Scripting and Remote Configuration: Since version 2.17.2, enabling scripting or loading remote configurations via protocols other than HTTPS requires explicit system property configuration for security reasons.

• Dependency and Module Changes:

  • SLF4J Binding: If you use SLF4J, you may need to update your SLF4J binding dependency. Log4j now provides different artifacts for SLF4J 1.7.x and newer versions (e.g., log4j-slf4j18-impl).
  • Removed Modules: The log4j-mongodb3, log4j-flume-ng, and log4j-kubernetes modules are no longer part of the main project and must be managed as separate dependencies.

• API Changes:

  • SSL Configuration: The API for SSL configuration has been updated to use a PasswordProvider instead of a String for passwords to enhance security.

Recommendation:

Given the mandatory Java version upgrade and multiple configuration changes, this upgrade carries a medium risk. Developers should:

1. Ensure the project is running on Java 8 or a later version.
2. Thoroughly review and test their Log4j configuration files for compatibility with the new version.
3. Update any dependencies for removed modules or SLF4J bindings as needed.
4. Check for usage of the SSL configuration API and update it to use PasswordProvider.

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.

[gwnlng]

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