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

[snykcareem]

Snyk has created this PR to fix 2 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-COMFASTERXMLJACKSONCORE-17440598	255	org.springframework.boot:spring-boot-starter-web: 2.6.6 -> 3.5.15 Major version upgrade No Path Found Proof of Concept
	Incomplete List of Disallowed Inputs SNYK-JAVA-COMFASTERXMLJACKSONCORE-17440366	182	org.springframework.boot:spring-boot-starter-web: 2.6.6 -> 3.5.15 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]

This major version upgrade from Spring Boot 2.6.6 to 3.x is a significant undertaking with multiple high-impact breaking changes. It requires a planned migration effort and cannot be merged without code and configuration modifications.

Key Breaking Changes:

• Java 17 Baseline: Spring Boot 3.0 requires Java 17 as the minimum JDK version. Applications must be upgraded from Java 8 or 11.
• Jakarta EE 9 Migration: This is the most impactful change. All Java EE APIs have been migrated from the javax.* namespace to the jakarta.* namespace. This requires updating all import statements for classes like javax.servlet.*, javax.persistence.*, and javax.validation.*.
• Spring Framework 6.0 Upgrade: Spring Boot 3.0 is built on Spring Framework 6.0, which introduces its own breaking changes. This includes the removal of deprecated classes, changes in AOP proxying for controllers, and updates to Servlet mocks.
• Spring Security 6.0: WebSecurityConfigurerAdapter has been removed in favor of a component-based, lambda DSL configuration. Authorization is now applied to every dispatch type by default.
• Configuration Property Changes: Numerous properties have been removed, renamed, or moved. For example, trailing slash matching is now disabled by default and the configuration property has been deprecated.
• Removed Auto-configurations: Support for CommonsMultipartResolver and Flapdoodle embedded MongoDB has been removed.

Recommendation:

This is a high-risk, high-effort migration. Do not merge directly. A dedicated migration plan is required.

1. Upgrade Incrementally: First, upgrade your application to the latest Spring Boot 2.7.x release to address deprecations before moving to 3.0.
2. Update JDK: Ensure your development and production environments are on Java 17.
3. Migrate to Jakarta EE: Use IDE tools or scripts to update all javax.* imports to jakarta.*.
4. Update Configuration: Use the spring-boot-properties-migrator module to identify and update changed configuration properties.
5. Refactor Spring Security: Rewrite security configurations using the new lambda-based approach.

Source: Spring Boot 3.0 Release Notes, 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.