[Snyk] Security upgrade org.springframework.boot:spring-boot-starter-web from 2.6.6 to 3.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
	Deserialization of Untrusted Data SNYK-JAVA-ORGSPRINGFRAMEWORK-18326609	181	org.springframework.boot:spring-boot-starter-web: 2.6.6 -> 3.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:

🦉 Deserialization of Untrusted Data

[snykcareem]

The upgrade from Spring Boot 2.6.6 to 3.0.0 is a major version change with significant breaking changes that require mandatory code and environment modifications.

Key Breaking Changes:

• Java 17 Baseline: Spring Boot 3.0 requires Java 17 as the minimum version. Applications must be running on JDK 17 or later.
• Jakarta EE 9/10 Migration: This is the most impactful change. Spring Boot 3.0 has migrated from Java EE to Jakarta EE. This requires changing all javax.* package imports to their new jakarta.* equivalents across the entire codebase. For example, javax.servlet.http.HttpServletRequest becomes jakarta.servlet.http.HttpServletRequest.
• Dependency Upgrades: This release is built on Spring Framework 6.0 and includes major version bumps for most core dependencies, including Spring Security 6.0, Spring Data 2022.0, and Hibernate 6.1. These transitive upgrades introduce their own breaking changes.
• Spring Security 6.0: WebSecurityConfigurerAdapter has been removed. Security configuration must be rewritten using a component-based approach, typically by defining a SecurityFilterChain bean.
• Configuration Properties: Numerous configuration properties have been renamed or removed. For example, server.max.http.header.size is now server.max-http-request-header-size.

Recommendation:
This is a high-effort migration. It is strongly recommended to first upgrade to the latest Spring Boot 2.7.x release to resolve deprecations before moving to 3.0. Utilize tools like the spring-boot-properties-migrator module and OpenRewrite recipes to automate parts of the migration, particularly for package renames and property changes.

Source: Spring Boot 3.0 Migration Guide, Spring Boot 3.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. 2 issues have been found so far.

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

[snykcareem]

✅ This PR has been automatically closed

The security issues addressed by this pull request are no longer present in the latest project scan. All vulnerabilities this PR was created to fix have been resolved through other means (e.g., dependency updates, direct fixes, or changes in vulnerability data).

Resolved Issues

• SNYK-JAVA-ORGSPRINGFRAMEWORK-18326609

What should I do?

No action is required. If you believe this PR was closed in error, you can reopen it and contact Snyk support.

---

This action was performed automatically by Snyk.