Repository navigation
Update Log4j security baseline while retaining Boot 2.1 logging bridges - #2
Merged
Merged
Conversation
loong10k
marked this pull request as ready for review
November 4, 2026 01:02
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both applications resolve Log4j Core 2.11.2 at compile scope through Boot's Log4j starter, within Apache's CVE-2021-44228 affected range. This confirms an affected dependency, not an exploitable deployment input path.
Override Boot's log4j2.version to Java 8 compatible 2.26.1, aligning API/Core/JUL/Web and the existing SLF4J 1.x bridge. Preserve Boot 2.1.4, SLF4J 1.7, public production API, deployment and JMX settings. Add real Boot logging initialization and Log4j/SLF4J/Spring JCL/JUL routing tests, literal message lookup and disabled default JNDI checks. CI checks actual dependency alignment and excludes circular/competing logging bridges.
Validation: Java 8/17/21 each passed all six tests locally. Effective POM/dependency checks passed. Validation stops at test; no images built/tagged/pushed, no deployment, no weakened security defaults.