[Snyk] Fix for 1 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• samples/server/petstore/jaxrs-resteasy/eap-joda/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.10.1 -> 2.21.2 com.fasterxml.jackson.core:jackson-databind: 2.10.1 -> 2.21.2 com.fasterxml.jackson.datatype:jackson-datatype-joda: 2.10.1 -> 2.21.2 org.jboss.resteasy:resteasy-jackson2-provider: 3.0.11.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

[snyk-io]

This upgrade contains a major version jump for org.jboss.resteasy:resteasy-jackson2-provider from 3.x to 6.x, which introduces significant breaking changes. The Jackson library upgrades are less critical but require verification of the Java runtime version.

High Risk: org.jboss.resteasy:resteasy-jackson2-provider (3.0.11.Final → 6.2.0.Final)

This is a major upgrade that crosses several breaking release series (4.x, 5.x, and 6.x). The most critical change is the migration from Java EE to Jakarta EE, which requires a namespace change in all application code.

Key Breaking Changes:

• Jakarta Namespace Migration: RESTEasy 6.x is built on Jakarta REST 3.x, which requires changing all Java imports from the javax.ws.rs.* package to jakarta.ws.rs.*. This is a mandatory code change that will cause compilation failures until all imports are updated.
• Module and Dependency Changes: RESTEasy has been restructured. The main resteasy-jaxrs module was deprecated and split into smaller modules like resteasy-core-spi and resteasy-client-api in version 4.x. Support for Spring and MicroProfile was moved to separate projects in version 5.x. You may need to update your build file's dependencies to include the new modules.
• Removed Providers: The legacy resteasy-jackson-provider (for Jackson 1.x), resteasy-jettison-provider, and resteasy-yaml-provider were removed in version 4.x.

Recommendation: This upgrade requires significant code and dependency modifications. Developers must refactor the application to use the jakarta.* namespace and verify that all necessary RESTEasy dependencies are correctly configured.

Medium Risk: Jackson Libraries (2.10.1 → 2.21.2)

This upgrade spans multiple minor versions of jackson-core, jackson-databind, and jackson-datatype-joda.

Key Changes:

• Java Version Requirement: Jackson 2.14 raised the minimum required Java version to JDK 8. Projects running on Java 7 will need to upgrade their runtime environment.
• Source Code Incompatibility: A stricter TypeReference handling was introduced in version 2.10, which can cause compilation failures in certain generic type assignment scenarios that previously worked.

While the Jackson 2.x series generally maintains API compatibility, the large version gap introduces a risk of behavioral changes from accumulated bug fixes that could affect application logic.

Recommendation: Verify that your project's Java version meets the Java 8 requirement. A thorough regression test is advised to catch any subtle behavioral changes.

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

[snyk-io]

⛔ Snyk checks have failed. 3 issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (3)
⛔	Open Source Security	0	0	3	0	3 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.