Skip to content

Comments

[Snyk] Upgrade org.apache.logging.log4j:log4j-core from 2.10.0 to 2.23.1#521

Open
tt9133github wants to merge 1 commit intomasterfrom
snyk-upgrade-c49f8bab18898c4d359e1cb54e78dc22
Open

[Snyk] Upgrade org.apache.logging.log4j:log4j-core from 2.10.0 to 2.23.1#521
tt9133github wants to merge 1 commit intomasterfrom
snyk-upgrade-c49f8bab18898c4d359e1cb54e78dc22

Conversation

@tt9133github
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade org.apache.logging.log4j:log4j-core from 2.10.0 to 2.23.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 28 versions ahead of your current version.
  • The recommended version was released 23 days ago, on 2024-03-06.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Remote Code Execution (RCE)
SNYK-JAVA-ORGAPACHELOGGINGLOG4J-2314720
929/1000
Why? Mature exploit, Has a fix available, CVSS 10
Mature
Remote Code Execution (RCE)
SNYK-JAVA-ORGAPACHELOGGINGLOG4J-2320014
929/1000
Why? Mature exploit, Has a fix available, CVSS 10
Mature
Denial of Service (DoS)
SNYK-JAVA-ORGAPACHELOGGINGLOG4J-2321524
929/1000
Why? Mature exploit, Has a fix available, CVSS 10
Proof of Concept
Arbitrary Code Execution
SNYK-JAVA-ORGAPACHELOGGINGLOG4J-2327339
929/1000
Why? Mature exploit, Has a fix available, CVSS 10
Proof of Concept
Man-in-the-Middle (MitM)
SNYK-JAVA-ORGAPACHELOGGINGLOG4J-567761
929/1000
Why? Mature exploit, Has a fix available, CVSS 10
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants