[Snyk] Security upgrade org.apache.logging.log4j:log4j-core from 2.14.1 to 2.25.3#21
Open
DavidThomas-coder wants to merge 1 commit intomainfrom
Open
[Snyk] Security upgrade org.apache.logging.log4j:log4j-core from 2.14.1 to 2.25.3#21DavidThomas-coder wants to merge 1 commit intomainfrom
DavidThomas-coder wants to merge 1 commit intomainfrom
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JAVA-ORGAPACHELOGGINGLOG4J-14532782
There was a problem hiding this comment.
This PR is being reviewed by Cursor Bugbot
Details
You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| <groupId>org.apache.logging.log4j</groupId> | ||
| <artifactId>log4j-core</artifactId> | ||
| <version>2.14.1</version> | ||
| <version>2.25.3</version> |
There was a problem hiding this comment.
Log4j version mismatch causes potential runtime failures
This security upgrade only updates log4j-core to 2.25.3 but leaves log4j-api at 2.14.1. Log4j requires both artifacts to be at the same version for binary compatibility. This mismatch will likely cause NoSuchMethodError or NoClassDefFoundError at runtime when log4j-core 2.25.3 attempts to call APIs that don't exist in the older log4j-api 2.14.1. The log4j-api dependency also needs to be upgraded to 2.25.3.
Additional Locations (1)
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
2 participants
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.
Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.
Snyk changed the following file(s):
log4shell-goof/log4shell-client/pom.xmlVulnerabilities that will be fixed with an upgrade:
SNYK-JAVA-ORGAPACHELOGGINGLOG4J-14532782
2.14.1->2.25.3No Known ExploitImportant
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.
Note
Security-focused dependency update with minimal scope.
org.apache.logging.log4j:log4j-corefrom2.14.1to2.25.3inlog4shell-client/pom.xmllog4j-apiremains at2.14.1Written by Cursor Bugbot for commit a15088a. This will update automatically on new commits. Configure here.