[Snyk] Security upgrade org.springframework.boot:spring-boot-starter-web from 2.6.6 to 4.0.0

[snykcareem]

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

Snyk changed the following file(s):

• converter-codegen-testapp/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Improper Authentication SNYK-JAVA-ORGAPACHETOMCATEMBED-16691231	159	org.springframework.boot:spring-boot-starter-web: 2.6.6 -> 4.0.0 Major version upgrade No Path Found No Known Exploit

Breaking Change Risk

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

[snykcareem]

This is a major version upgrade from Spring Boot 2.6.6 to a hypothetical 4.0.0. This leap crosses two major, highly impactful releases: 3.0 and 4.0. The upgrade requires significant developer action due to fundamental platform changes.

Spring Boot 3.0 Breaking Changes:

• Java 17 Baseline: Spring Boot 3.0 requires Java 17 as a minimum version. Applications must be upgraded from any previous Java version.
• Jakarta EE 9 Migration: This is a critical breaking change. All javax.* packages have been replaced with jakarta.* packages. This requires a codebase-wide update of imports for APIs like JPA (javax.persistence), Servlet API (javax.servlet), and Bean Validation (javax.validation).
• Configuration Properties: Many configuration properties have been renamed or removed. While the spring-boot-properties-migrator module can help identify and temporarily migrate these, the underlying application.properties or application.yml files must be updated.
• Removed Deprecations: All code deprecated in the 2.x line has been removed.
• Spring Security 6.0: The upgrade to Spring Security 6.0 introduces its own set of breaking changes that will likely require security configuration updates.

Spring Boot 4.0 Breaking Changes:

• Java 21+ Baseline: Spring Boot 4.0 requires Java 21 as the minimum version, with first-class support for Java 25.
• Spring Framework 7 & Jakarta EE 11: The framework is built on Spring Framework 7 and targets Jakarta EE 11, requiring a Servlet 6.1 compatible container.
• Configuration Changes: New configuration properties have been introduced for features like API versioning and HTTP Service Clients, and some properties have been renamed.

Recommendation: This upgrade cannot be performed directly. A step-by-step migration is required:

1. First, upgrade the application from 2.6.x to the latest 2.7.x release.
2. Then, perform the migration from 2.7.x to Spring Boot 3.x. This will involve upgrading to Java 17, migrating all javax imports to jakarta, updating configuration properties, and addressing removed deprecations.
3. Finally, plan the migration from Spring Boot 3.x to 4.x, which includes upgrading to Java 21+ and adapting to new framework features and configuration models.

Source: Spring Boot 3.0 Release Notes, Spring Boot 4.0 Release Notes

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

[snykcareem]

⛔ Snyk checks have failed. 4 issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (4)
⛔	Open Source Security	0	4	0	0	4 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.

[m-abdelmohsen]

Closing this PR as it has been inactive for a long period. Please reopen if this is still relevant.