Skip to content
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

[Snyk] Upgrade org.apache.logging.log4j:log4j-core from 2.17.1 to 2.22.1 #339

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

megaeasex
Copy link

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.17.1 to 2.22.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 8 versions ahead of your current version.
  • The recommended version was released 2 months ago, on 2023-12-22.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Stack-based Buffer Overflow
SNYK-JAVA-ORGYAML-3016888
292/1000
Why? Proof of Concept exploit, CVSS 3.7
Proof of Concept
Stack-based Buffer Overflow
SNYK-JAVA-ORGYAML-3113851
292/1000
Why? Proof of Concept exploit, CVSS 3.7
No Known Exploit
Creation of Temporary File in Directory with Insecure Permissions
SNYK-JAVA-COMGOOGLEGUAVA-5710356
292/1000
Why? Proof of Concept exploit, CVSS 3.7
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