SWI-3723 [Snyk] Fix for 1 vulnerabilities

[bwappsec]

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

Snyk changed the following file(s):

• modules/openapi-generator-maven-plugin/examples/multi-module/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-15365924	170	com.fasterxml.jackson.core:jackson-core: 2.19.2 -> 2.21.1 com.fasterxml.jackson.core:jackson-databind: 2.19.2 -> 2.21.1 com.fasterxml.jackson.datatype:jackson-datatype-joda: 2.19.2 -> 2.21.1 com.fasterxml.jackson.datatype:jackson-datatype-jsr310: 2.19.2 -> 2.21.1 com.fasterxml.jackson.jaxrs:jackson-jaxrs-base: 2.19.2 -> 2.21.1 org.glassfish.jersey.media:jersey-media-json-jackson: 2.35 -> 3.0.4 Major version upgrade No Path Found Proof of Concept

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:

🦉 Allocation of Resources Without Limits or Throttling

[bwappsec]

This set of upgrades includes a major version increase for org.glassfish.jersey.media:jersey-media-json-jackson from 2.35 to 3.0.4, which introduces significant breaking changes. The Jackson library upgrades are minor and considered low-risk.

High Risk: org.glassfish.jersey.media:jersey-media-json-jackson (2.35 → 3.0.4)

The upgrade to Jersey 3.x aligns with the transition from Java EE to Jakarta EE. This requires code and environment changes.

• Namespace Migration: The most critical breaking change is the package namespace migration from javax.* to jakarta.*. All imports using javax.ws.rs.* and other related javax packages must be updated to their jakarta.* equivalents.
• Environment Requirements: Jersey 3.0 requires a Jakarta EE 9 compatible application server (e.g., Tomcat 10+, Jetty 11+). Furthermore, the 3.x line has stricter JDK requirements, with Jersey 3.1+ requiring a minimum of JDK 11.
• Removed APIs: Support for Jackson 1.x has been removed.

Recommendation: Before merging, developers must refactor the application to use the new jakarta.* namespaces. The deployment environment must also be verified to ensure it meets the new application server and JDK requirements.

Low Risk: Jackson Upgrades (2.19.2 → 2.21.1)

The upgrades for jackson-core, jackson-databind, and other modules are minor versions. According to the release notes, version 2.21 is a Long-Term Support (LTS) release that contains mostly bug fixes and new, non-breaking features. No mandatory code changes are required for these updates.

Source: Jersey 3.x Migration Guide, Jackson 2.21 Release Notes

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.