Skip to content

[Snyk] Fix for 2 vulnerabilities#1556

Open
macroscope-cloud wants to merge 1 commit into
snyk-fix-b36ab82cb3394caf6c17794115565a82from
snyk-fix-c68149ec2659e1b5d8098e7b2ff6223b
Open

[Snyk] Fix for 2 vulnerabilities#1556
macroscope-cloud wants to merge 1 commit into
snyk-fix-b36ab82cb3394caf6c17794115565a82from
snyk-fix-c68149ec2659e1b5d8098e7b2ff6223b

Conversation

@macroscope-cloud

Copy link
Copy Markdown

snyk-top-banner

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

Snyk changed the following file(s):

  • examples/iOS-Hybrid-App-Java-Server/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
high severity Improper Authentication
SNYK-JAVA-ORGAPACHETOMCATEMBED-17732890
  726   org.apache.tomcat.embed:tomcat-embed-core:
11.0.11 -> 11.0.23
org.apache.tomcat.embed:tomcat-embed-websocket:
11.0.11 -> 11.0.23
org.springframework.boot:spring-boot-starter-tomcat:
3.5.5 -> 4.0.0
Major version upgrade No Known Exploit
high severity Detection of Error Condition Without Action
SNYK-JAVA-ORGAPACHETOMCATEMBED-17733746
  721   org.apache.tomcat.embed:tomcat-embed-core:
11.0.11 -> 11.0.23
org.apache.tomcat.embed:tomcat-embed-websocket:
11.0.11 -> 11.0.23
org.springframework.boot:spring-boot-starter-tomcat:
3.5.5 -> 4.0.0
Major version upgrade No Known Exploit

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


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 Authentication

@macroscope-cloud

Copy link
Copy Markdown
Author

Merge Risk: High

The upgrade from spring-boot-starter-tomcat 3.5.5 to 4.0.0 is a major platform migration with significant breaking changes. The Tomcat embed upgrades are minor patches included as part of this larger, high-risk update.

Key Breaking Changes in Spring Boot 4.0:

  • Environment Requirements: Spring Boot 4.0 requires Java 17 or later (first-class support for Java 25 is also noted) and is built on Spring Framework 7 and the Jakarta EE 11 platform, which necessitates a Servlet 6.1 compatible container. [2, 8, 10]
  • Major Dependency Upgrades: This upgrade cascades to new major versions of critical libraries, including Jackson 3, Hibernate 7, and Spring Security 7. These bring their own breaking changes. [1, 9]
  • API Removals and Modularization: APIs deprecated in the 3.x line have been removed. The framework is now more modular, which may require adding new, more specific starter dependencies (e.g., for WebClient or tests) to your build. [11, 14]
  • Configuration Property Changes: Numerous configuration properties have been renamed or removed. Using the spring-boot-properties-migrator module is highly recommended to help identify and update properties in application.properties or application.yml. [4, 8]
  • Undertow Server Removed: Support for Undertow as an embedded server has been removed due to its incompatibility with the required Servlet 6.1 baseline. Projects using it must migrate to Tomcat or Jetty. [9, 13]
  • Jackson 3 Migration: The default JSON library is now Jackson 3, which introduces a new package namespace and API changes. This is a common source of migration issues. [1, 11]

Recommendation: This is a high-effort upgrade that requires significant code and configuration changes. Before upgrading to 4.0.0, you should first upgrade to the latest Spring Boot 3.5.x release and resolve all deprecation warnings. [8, 12]

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

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