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] Fix for 3 vulnerabilities #35

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

Conversation

Exnadella
Copy link
Owner

@Exnadella Exnadella commented Dec 22, 2024

User description

snyk-top-banner

Snyk has created this PR to fix 3 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
medium severity Improper Neutralization of Special Elements
SNYK-JAVA-CHQOSLOGBACK-8539866
  581   ch.qos.logback:logback-classic:
1.2.13 -> 1.5.13
ch.qos.logback:logback-core:
1.2.13 -> 1.5.13
No Known Exploit
medium severity Improper Neutralization of Special Elements
SNYK-JAVA-CHQOSLOGBACK-8539867
  581   ch.qos.logback:logback-classic:
1.2.13 -> 1.5.13
No Known Exploit
low severity Server-side Request Forgery (SSRF)
SNYK-JAVA-CHQOSLOGBACK-8539865
  406   ch.qos.logback:logback-classic:
1.2.13 -> 1.5.13
ch.qos.logback:logback-core:
1.2.13 -> 1.5.13
No Known Exploit

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

🦉 Server-side Request Forgery (SSRF)


PR Type

Bug fix


Description

  • Fixed 3 security vulnerabilities in Logback dependencies by upgrading to version 1.5.13
  • Addressed medium severity issues related to Improper Neutralization of Special Elements
  • Updated both logback-core and logback-classic packages to the same version

Changes walkthrough 📝

Relevant files
Dependencies
pom.xml
Upgrade Logback dependencies to fix security vulnerabilities

pom.xml

  • Updated ch.qos.logback:logback-core from version 1.2.13 to 1.5.13
  • Updated ch.qos.logback:logback-classic from version 1.2.13 to 1.5.13
  • +2/-2     

    💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

    Copy link

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ Recommended focus areas for review

    Version Compatibility

    The major version upgrade of logback from 1.2.x to 1.5.x may introduce breaking changes. Verify that the application still works as expected with the new version.

          <version>1.5.13</version>
        </dependency>
    
        <dependency>
          <groupId>ch.qos.logback</groupId>
          <artifactId>logback-classic</artifactId>
          <version>1.5.13</version>

    Copy link

    PR Code Suggestions ✨

    No code suggestions found for the PR.

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

    Successfully merging this pull request may close these issues.

    2 participants