Skip to content

SWI-3723 [Snyk] Fix for 7 vulnerabilities#1204

Open
bwappsec wants to merge 1 commit intomasterfrom
snyk-fix-5f8106b133bdc351491498b236df460b
Open

SWI-3723 [Snyk] Fix for 7 vulnerabilities#1204
bwappsec wants to merge 1 commit intomasterfrom
snyk-fix-5f8106b133bdc351491498b236df460b

Conversation

@bwappsec
Copy link
Copy Markdown

snyk-top-banner

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

Snyk changed the following file(s):

  • samples/server/petstore/java-pkmst/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
critical severity HTTP Request Smuggling
SNYK-JAVA-ORGECLIPSEJETTY-16061843
  226   Major version upgrade No Path Found Proof of Concept
high severity Improper Authentication
SNYK-JAVA-ORGAPACHETOMCATEMBED-15989808
  145   Major version upgrade No Path Found No Known Exploit
high severity Improper Authentication
SNYK-JAVA-ORGAPACHETOMCATEMBED-15989820
  130   Major version upgrade No Path Found No Known Exploit
high severity HTTP Request Smuggling
SNYK-JAVA-ORGAPACHETOMCATEMBED-15990633
  110   Major version upgrade No Path Found No Known Exploit
medium severity Improper Encoding or Escaping of Output
SNYK-JAVA-ORGAPACHELOGGINGLOG4J-15967769
  50   net.masterthought:cucumber-reporting:
3.10.0 -> 3.17.1
No Path Found No Known Exploit
medium severity Improper Encoding or Escaping of Output
SNYK-JAVA-ORGAPACHELOGGINGLOG4J-15967804
  50   net.masterthought:cucumber-reporting:
3.10.0 -> 3.17.1
No Path Found No Known Exploit
medium severity Improper Encoding or Escaping of Output
SNYK-JAVA-ORGAPACHETOMCATEMBED-15989812
  44   Major version upgrade No Path Found No Known Exploit

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.

Vulnerabilities that could not be fixed

  • Upgrade:
    • Could not upgrade org.springframework.boot:spring-boot-starter-jetty@1.5.6.RELEASE to org.springframework.boot:spring-boot-starter-jetty@3.2.0; Reason could not apply upgrade, dependency is managed externally ; Location: https://maven-central.storage-download.googleapis.com/maven2/org/springframework/boot/spring-boot-dependencies/1.5.6.RELEASE/spring-boot-dependencies-1.5.6.RELEASE.pom
  • Could not upgrade org.springframework.boot:spring-boot-starter-web@1.5.6.RELEASE to org.springframework.boot:spring-boot-starter-web@4.0.0; Reason could not apply upgrade, dependency is managed externally ; Location: https://maven-central.storage-download.googleapis.com/maven2/org/springframework/boot/spring-boot-dependencies/1.5.6.RELEASE/spring-boot-dependencies-1.5.6.RELEASE.pom

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:

🦉 Improper Encoding or Escaping of Output
🦉 Improper Authentication

@bwappsec
Copy link
Copy Markdown
Author

Merge Risk: High

This upgrade contains multiple major version jumps for critical Spring Boot starters, introducing significant breaking changes that require substantial migration effort.

Top 3 Most Impactful Upgrades:

  • org.springframework.boot:spring-boot-starter-web 1.5.6.RELEASE4.0.0 (HIGH)
  • org.springframework.boot:spring-boot-starter-jetty 1.5.6.RELEASE3.2.0 (HIGH)

These two upgrades represent a multi-generational leap from Spring Boot 1.5 to Spring Boot 3.x (as 4.0 is not yet released). This is a major undertaking with several layers of breaking changes. It is strongly recommended to upgrade incrementally (e.g., 1.5 -> 2.0 -> 2.7 -> 3.2) rather than in one jump.

Key Breaking Changes:

  • Java 17 Required: Spring Boot 3.0 requires Java 17 as a minimum, ending support for Java 8 and 11.
  • Jakarta EE Migration: All dependencies have migrated from Java EE to Jakarta EE. This requires changing all javax.* package imports to jakarta.* throughout the application. This is a significant, codebase-wide change.
  • Configuration Properties: Numerous configuration properties have been renamed or removed. The spring-boot-properties-migrator module can help identify and temporarily migrate these.
  • Spring Security 6.0: Authorization is now applied to every dispatch type by default, which may affect security configurations.
  • Removed Deprecations: All APIs deprecated in Spring Boot 2.x have been removed in version 3.0.
  • net.masterthought:cucumber-reporting 3.10.03.17.1 (LOW)

This is a minor version upgrade. While the official release notes were not found, the scope of changes between minor versions in this library is typically focused on bug fixes and small feature additions. No significant breaking changes are expected for this range.

Recommendation: The Spring Boot upgrade is a major project and should not be merged without a dedicated migration and testing plan. Developers must address the Java version, Jakarta EE namespace changes, and updated configurations. Use the official migration guides and the properties migrator tool to assist with the process.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@bwappsec bwappsec changed the title [Snyk] Fix for 7 vulnerabilities SWI-3723 [Snyk] Fix for 7 vulnerabilities Apr 16, 2026
@bwappsec
Copy link
Copy Markdown
Author

bwappsec commented Apr 16, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

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