SWI-3723 [Snyk] Security upgrade io.vertx:vertx-rx-java from 3.5.2 to 4.5.23

[bwappsec]

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

Snyk changed the following file(s):

• samples/client/petstore/java/vertx-no-nullable/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	CRLF Injection SNYK-JAVA-IONETTY-14423947	69	io.vertx:vertx-rx-java: 3.5.2 -> 4.5.23 Major version upgrade No Path Found No Known Exploit

---

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:

🦉 CRLF Injection

[bwappsec]

This is a major version upgrade from Vert.x 3 to Vert.x 4, which introduces significant breaking changes and requires code refactoring.

Key Changes:

• Asynchronous Operations: Vert.x 4 introduces a Future<T> based API for asynchronous operations, which exists alongside the legacy callback-based model. Many APIs have been updated to return Futures, changing how asynchronous code is written and composed. [1, 7]
• API Removals: APIs that were deprecated in Vert.x 3.x have been removed in version 4. For example, the synchronous HttpServerRequest.upgrade() method has been removed in favor of the asynchronous toWebSocket(). [1, 2]
• Core API Changes: Several core interfaces have changed. For instance, WriteStream.write() is no longer a fluent method, and MessageProducer no longer extends WriteStream. [1]

Source: Vert.x 4 Migration Guide
Recommendation: This upgrade cannot be completed by simply changing the version number. Developers must follow the official migration guide to refactor the application, addressing removed APIs and adapting to the new Future-based asynchronous model.

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	Scanner	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.