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

[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
	Missing Critical Step in Authentication SNYK-JAVA-ORGAPACHETOMCATEMBED-17733813	178	org.springframework.boot:spring-boot-starter-web: 2.6.6 -> 3.3.10 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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[snykcareem]

The upgrade from Spring Boot 2.6.6 to 3.3.10 is a major migration with significant breaking changes that require substantial developer effort. This is not a drop-in replacement and will require code, configuration, and environment updates.

Key Breaking Changes:

• Java 17 Required: Spring Boot 3.x requires Java 17 as the minimum JDK version. Applications must be migrated from older Java versions like 8 or 11.

• Jakarta EE Namespace Migration: This is the most pervasive code change. All Java EE package imports must be changed from javax.* to jakarta.*. This affects core components used in spring-boot-starter-web, such as the Servlet API (javax.servlet.* becomes jakarta.servlet.*).

• Spring Framework 6 & Spring Security 6: This upgrade is built on Spring Framework 6 and Spring Security 6, which introduce their own breaking changes. All code deprecated in previous versions has been removed.

• URL Matching Behavior: The default strategy for URL matching has changed and is stricter. Trailing slashes in request paths are no longer matched by default. For example, a controller mapped to /api/users will no longer match a request to /api/users/. This can lead to unexpected 404 Not Found errors.

• Configuration Property Changes: Numerous configuration properties in application.properties or application.yml have been renamed or removed. For example, server.max.http.header.size is now server.max-http-request-header-size.

• Auto-Configuration Registration: The method for registering custom auto-configurations in spring.factories has been removed and replaced by an .imports file.

Recommendation:
This is a high-risk, high-effort migration. It is strongly recommended to first upgrade to the latest Spring Boot 2.7.x release before attempting the migration to 3.x. Developers should use automated tooling like OpenRewrite recipes and the spring-boot-properties-migrator module to assist with the migration. Extensive testing will be required to validate all application functionality, especially around API endpoints, security, and data access.

Source: Spring Boot 3.0 Migration Guide

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	1	3	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.