SWI-3723 [Snyk] Fix for 3 vulnerabilities #715
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to fix 3 vulnerabilities in the maven dependencies of this project.
Snyk changed the following file(s):
samples/server/petstore/java-pkmst/pom.xmlThis release includes two major, high-risk upgrades that require significant developer action before merging.
org.springframework.boot:spring-boot-starter-web(1.5.6.RELEASE → 3.4.11): This is a massive upgrade across two major versions (1.x → 2.x → 3.x). Key breaking changes include a required upgrade to Java 17 and the migration from Java EE to Jakarta EE, which renames packages fromjavax.*tojakarta.*across the entire codebase. Numerous configuration properties and core dependencies like Spring Security have also changed significantly.net.logstash.logback:logstash-logback-encoder(4.11 → 9.0): This upgrade also spans multiple major versions. Version 8.0 and newer require Java 11. Given the Spring Boot upgrade requires Java 17, this is compatible, but configuration and class name changes are highly likely across this many versions.Recommendation: These upgrades are substantial and will require a dedicated migration effort. It is strongly advised to handle this in a separate, focused effort and not as part of routine dependency updates. Developers should follow the official Spring Boot 2.x to 3.x migration guides.
Vulnerabilities that will be fixed with an upgrade:
SNYK-JAVA-ORGAPACHETOMCATEMBED-13733966
Major version upgradeNo Path FoundNo Known ExploitSNYK-JAVA-ORGAPACHETOMCATEMBED-13723930
Major version upgradeNo Path FoundNo Known ExploitSNYK-JAVA-CHQOSLOGBACK-13169722
4.11->9.0Major version upgradeNo Path FoundNo Known ExploitVulnerabilities that could not be fixed
org.springframework.boot:[email protected]toorg.springframework.boot:[email protected]; Reasoncould 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.pomImportant
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:
🦉 Relative Path Traversal