[Snyk] Security upgrade com.fasterxml.jackson.core:jackson-databind from 2.9.3 to 2.21.2

[philvarner-snyk]

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

Snyk changed the following file(s):

• 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-databind: 2.9.3 -> 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

[philvarner-snyk]

This upgrade from version 2.9.3 to 2.21.2 spans multiple minor versions and introduces several significant breaking changes, including a Java runtime requirement update, source-incompatible API changes, and new default processing limits.

Key Breaking Changes:

• Java 8 Required: Starting from version 2.13, jackson-databind requires Java 8 or newer. The previous version (2.9.x) only required Java 7.
• Source Incompatible API Changes:
  • v2.10: A change to ObjectMapper.readValue() now enforces stricter generic type assignment for TypeReference, which can lead to compilation failures where it previously worked.
  • v2.12: The treeToValue() method no longer throws a checked JsonProcessingException, which is a source-breaking change for any code that was catching this specific exception.
• New Processing Limits: To address security vulnerabilities (CVEs), version 2.15 introduced default limits on the maximum size of processed data, including string length and nesting depth. This can cause JsonProcessingException for applications that handle very large or deeply nested JSON documents.
• Behavioral Changes:
  • v2.11: The default serialization format for java.util.Date and java.util.Calendar timezone offsets now includes a colon (e.g., +00:00 instead of +0000).
  • v2.13: Arrays.asList() deserialization now produces an immutable list, which will cause runtime exceptions if the code attempts to modify it.
  • v2.15: Deserialization of Java Record types was changed, which could break existing logic for users of this feature.

Recommendation:

Due to the number of source and behavioral breaking changes, this upgrade requires careful validation. Developers should:

1. Ensure the project is running on Java 8 or newer.
2. Review code for usage of readValue() with TypeReference and treeToValue() to fix potential compilation issues.
3. Test applications that process large JSON documents to ensure they do not exceed the new default processing limits. If they do, StreamReadConstraints may need to be configured on the JsonFactory.
4. Thoroughly test all serialization and deserialization logic, paying special attention to dates, Java Records, and any code that modifies lists returned from deserialization.

Source: Jackson 2.x Release Notes

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

[philvarner-snyk]

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