[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/client/petstore/java/resttemplate/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.jaxrs:jackson-jaxrs-json-provider: 2.10.1 -> 2.21.2 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 of the Jackson JSON processing library from version 2.10.1 to 2.21.2 includes several important changes that require developer attention. While this is not a major version upgrade, there are environmental requirements and behavioral changes that could impact applications.

Key Changes:

• Java Version Requirement: The baseline Java version has been increased. Starting from version 2.13, jackson-databind requires Java 8. As of version 2.14, jackson-core also requires Java 8. Projects running on older Java versions must upgrade their environment.

• Jakarta EE Namespace: For users of jackson-jaxrs-json-provider, version 2.13 introduced a separate set of artifacts for the jakarta.* namespace. If your application runs on a modern application server that uses Jakarta EE (like Tomcat 10+, WildFly 27+), you must switch your dependency to the jackson-jaxrs-jakarta-json-provider artifact.

• New Processing Limits: To improve security against Denial of Service (DoS) attacks, version 2.15 introduced default limits on the complexity of incoming JSON. This includes limits on the maximum string length, number length, and nesting depth. Applications processing very large or deeply nested JSON documents may need to adjust the StreamReadConstraints on the JsonFactory.

• Behavioral Change with @JsonIgnore: In version 2.14, the handling of conflicting @JsonIgnore and @JsonProperty annotations across a class hierarchy was changed. @JsonIgnore is now given higher precedence, which could change what fields are included in the serialized output.

Recommendation:

• Verify that your project's JRE is Java 8 or newer.
• If using JAX-RS, check if your application server uses the javax.* or jakarta.* namespace and ensure you are using the correct Jackson JAX-RS provider artifact.
• Test your application's JSON processing to ensure it is not negatively impacted by the new processing limits or the change in annotation behavior.

Source: Jackson Project Release Notes

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

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