-
Notifications
You must be signed in to change notification settings - Fork 0
[Snyk] Upgrade org.apache.logging.log4j:log4j-core from 2.13.3 to 2.25.1 #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -66,7 +66,7 @@ | |
| <dependency> | ||
| <groupId>org.apache.logging.log4j</groupId> | ||
| <artifactId>log4j-core</artifactId> | ||
| <version>2.13.3</version> | ||
| <version>2.25.1</version> | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ℹ️ Additional Security Considerations: While reviewing the dependencies, I noticed several other components that may benefit from security updates: JUnit 4.13.1 (consider upgrading to 4.13.2 or JUnit 5), Mockito 1.10.19 (very outdated), and the JSON library 20200518. Consider running a comprehensive dependency security scan to identify other potential vulnerabilities. |
||
| </dependency> | ||
| <dependency> | ||
| <groupId>org.mockito</groupId> | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ Security Upgrade: This Log4j version upgrade is critical and addresses multiple severe security vulnerabilities1234. The upgrade from 2.13.3 to 2.25.1 resolves two critical Remote Code Execution vulnerabilities, one high-severity Denial of Service vulnerability, and one medium-severity Arbitrary Code Execution vulnerability. This change should be prioritized for immediate deployment.
Footnotes
CWE-94: Code Injection - https://cwe.mitre.org/data/definitions/94.html ↩
CWE-502: Deserialization of Untrusted Data - https://cwe.mitre.org/data/definitions/502.html ↩
CWE-400: Uncontrolled Resource Consumption - https://cwe.mitre.org/data/definitions/400.html ↩
CWE-20: Improper Input Validation - https://cwe.mitre.org/data/definitions/20.html ↩