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):

• samples/client/echo_api/java/resteasy/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-15907551	125	com.fasterxml.jackson.core:jackson-core: 2.19.2 -> 2.21.2 com.fasterxml.jackson.core:jackson-databind: 2.19.2 -> 2.21.2 com.fasterxml.jackson.datatype:jackson-datatype-jsr310: 2.19.2 -> 2.21.2 org.jboss.resteasy:resteasy-jackson2-provider: 4.7.6.Final -> 6.2.0.Final 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:

🦉 Allocation of Resources Without Limits or Throttling

[bwappsec]

This set of upgrades includes a major and breaking version change for resteasy-jackson2-provider from 4.x to 6.x. The Jackson library upgrades are minor and considered low-risk.

org.jboss.resteasy:resteasy-jackson2-provider 4.7.6.Final → 6.2.0.Final (HIGH RISK)

This is a significant major version upgrade that requires code and dependency changes. The primary breaking change is the transition from Jakarta EE 8 to Jakarta EE 9/10, which involves a full namespace migration.

• javax.* to jakarta.* Namespace Change: RESTEasy 6.x is built on Jakarta REST 3.x, which uses the jakarta.* package namespace instead of the older javax.* namespace. All imports for JAX-RS APIs (e.g., javax.ws.rs.*) must be updated to their jakarta.ws.rs.* equivalents.
• Module Separation: Support for Spring and MicroProfile has been moved out of the core RESTEasy project into separate artifacts (resteasy-spring and resteasy-microprofile). If your project uses this functionality, you will need to add these new dependencies.

Recommendation: Before merging, developers must update all javax.ws.rs.* imports to jakarta.ws.rs.*. Additionally, verify if you need to add the new resteasy-spring or resteasy-microprofile dependencies.

Source: RESTEasy 4.x to 6.x Migration Guide, RESTEasy Announcements

Jackson Upgrades 2.19.2 → 2.21.2 (LOW RISK)

The upgrades for jackson-core, jackson-databind, and jackson-datatype-jsr310 are minor version bumps. The release notes for versions 2.20 and 2.21 indicate that these are smaller releases focused on bug fixes, performance improvements, and preparations for Jackson 3.0. No significant breaking API changes or mandatory actions are required for this upgrade.

Source: Jackson 2.20 Release Notes, 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	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.

[bwappsec]

✅ 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-COMFASTERXMLJACKSONCORE-15907551

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.