Skip to content

[Snyk] Fix for 8 vulnerabilities#30

Open
tessoudali wants to merge 1 commit intomasterfrom
snyk-fix-289a89686dec249047b7f245452e5645
Open

[Snyk] Fix for 8 vulnerabilities#30
tessoudali wants to merge 1 commit intomasterfrom
snyk-fix-289a89686dec249047b7f245452e5645

Conversation

@tessoudali
Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 8 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
high severity Path Traversal
SNYK-JAVA-ORGSPRINGFRAMEWORK-8230373
  585   org.springframework:spring-webmvc:
4.2.6.RELEASE -> 6.1.14
Major version upgrade No Path Found No Known Exploit
medium severity Authorization Bypass
SNYK-JAVA-ORGSPRINGFRAMEWORKSECURITY-8399269
  515   org.springframework.security:spring-security-config:
4.1.0.RELEASE -> 6.2.7
org.springframework.security:spring-security-web:
4.1.0.RELEASE -> 6.2.7
Major version upgrade No Path Found No Known Exploit
medium severity Authorization Bypass
SNYK-JAVA-ORGSPRINGFRAMEWORKSECURITY-8399272
  515   org.springframework.security:spring-security-config:
4.1.0.RELEASE -> 6.2.7
Major version upgrade No Path Found No Known Exploit
medium severity Authorization Bypass
SNYK-JAVA-ORGSPRINGFRAMEWORKSECURITY-8399278
  515   org.springframework.security:spring-security-web:
4.1.0.RELEASE -> 6.2.7
Major version upgrade No Path Found No Known Exploit
low severity Improper Handling of Case Sensitivity
SNYK-JAVA-ORGSPRINGFRAMEWORK-8230364
  265   org.springframework.data:spring-data-jpa:
1.10.1.RELEASE -> 3.2.11
org.springframework.security:spring-security-config:
4.1.0.RELEASE -> 6.2.7
org.springframework.security:spring-security-web:
4.1.0.RELEASE -> 6.2.7
org.springframework:spring-webmvc:
4.2.6.RELEASE -> 6.1.14
Major version upgrade No Path Found No Known Exploit
low severity Improper Handling of Case Sensitivity
SNYK-JAVA-ORGSPRINGFRAMEWORK-8230365
  265   org.springframework.data:spring-data-jpa:
1.10.1.RELEASE -> 3.2.11
org.springframework.security:spring-security-config:
4.1.0.RELEASE -> 6.2.7
org.springframework.security:spring-security-web:
4.1.0.RELEASE -> 6.2.7
org.springframework:spring-orm:
4.2.6.RELEASE -> 6.1.14
org.springframework:spring-webmvc:
4.2.6.RELEASE -> 6.1.14
Major version upgrade No Path Found No Known Exploit
low severity Improper Handling of Case Sensitivity
SNYK-JAVA-ORGSPRINGFRAMEWORK-8230366
  265   org.springframework.security:spring-security-web:
4.1.0.RELEASE -> 6.2.7
org.springframework:spring-webmvc:
4.2.6.RELEASE -> 6.1.14
Major version upgrade No Path Found No Known Exploit
low severity Improper Handling of Case Sensitivity
SNYK-JAVA-ORGSPRINGFRAMEWORK-8230368
  265   org.springframework:spring-webmvc:
4.2.6.RELEASE -> 6.1.14
Major version upgrade No Path Found 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:

🦉 Path Traversal

@deno-deploy deno-deploy bot had a problem deploying to Preview November 24, 2024 06:04 Failure
@vercel
Copy link
Copy Markdown

vercel bot commented Nov 24, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
ifttt-clone ❌ Failed (Inspect) Nov 24, 2024 6:04am
ifttt-clone-amq8 ❌ Failed (Inspect) Nov 24, 2024 6:04am
ifttt-clone-aurk ❌ Failed (Inspect) Nov 24, 2024 6:04am

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