SWI-3723 [Snyk] Security upgrade org.springframework.boot:spring-boot-starter-webflux from 2.7.17 to 3.5.12

[bwappsec]

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

Snyk changed the following file(s):

• samples/client/petstore/java/webclient-swagger2/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Directory Traversal SNYK-JAVA-ORGSPRINGFRAMEWORK-15701844	111	org.springframework.boot:spring-boot-starter-webflux: 2.7.17 -> 3.5.12 Major version upgrade No Path Found No Known Exploit
	Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') SNYK-JAVA-ORGSPRINGFRAMEWORK-15701755	29	org.springframework.boot:spring-boot-starter-webflux: 2.7.17 -> 3.5.12 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:

🦉 Directory Traversal

[bwappsec]

This is a major version upgrade from Spring Boot 2.7.17 to 3.5.12, which introduces significant breaking changes and requires several migration steps. The upgrade is based on Spring Framework 6.0 and requires Java 17 as a minimum version.

Key Breaking Changes:

• Java 17 Baseline: Spring Boot 3.0 requires Java 17 or later. Applications must be upgraded from older Java versions like 8 or 11.
• Jakarta EE 9 Migration: All Java EE APIs have been replaced with their Jakarta EE equivalents. This requires a major refactoring of import statements from javax.* to jakarta.* across the entire codebase.
• Configuration Properties Migration: Numerous configuration properties have been renamed or removed. For example, server.max.http.header.size is now server.max-http-request-header-size, and properties for Redis and Cassandra have moved. Spring Boot provides a spring-boot-properties-migrator module to help identify and temporarily migrate these properties at runtime.
• Spring Security 6.0: Spring Boot 3.0 uses Spring Security 6.0, which has its own set of breaking changes. It is recommended to first upgrade to Spring Security 5.8 within your Spring Boot 2.7 application before migrating to version 6.0.
• URL Matching Changes: As of Spring Framework 6.0, trailing slash matching is disabled by default. This means a controller mapping for /endpoint will no longer match /endpoint/.
• Auto-configuration Registration: The method for registering auto-configurations in spring.factories has been removed. Developers must now use the META-INF/spring/org.springframework.boot.autoconfigure.AutoConfiguration.imports file.

WebFlux Specific Changes:

• As part of the broader Spring Framework 6.0 changes, controller detection is stricter and now requires a @Controller annotation; a type-level @RequestMapping is no longer sufficient.

Source: Spring Boot 3.0 Migration Guide

Recommendation: This is a high-risk upgrade that requires significant developer effort. It is critical to follow the official migration guide. Start by upgrading to the latest Spring Boot 2.7.x release, then upgrade to Java 17, and finally tackle the migration to Spring Boot 3.x, paying close attention to the Jakarta EE namespace changes and updated configuration properties.

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

[bwappsec]

✅ Snyk checks have passed. No issues have been found so far.

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