[Snyk] Security upgrade com.fasterxml.jackson.core:jackson-databind from 2.10.0 to 2.18.8

[snyk-io]

Snyk has created this PR to fix 2 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
	Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-17440598	340	com.fasterxml.jackson.core:jackson-databind: 2.10.0 -> 2.18.8 No Path Found Proof of Concept
	Incomplete List of Disallowed Inputs SNYK-JAVA-COMFASTERXMLJACKSONCORE-17440366	242	com.fasterxml.jackson.core:jackson-databind: 2.10.0 -> 2.18.8 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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[snyk-io]

This upgrade from version 2.10.0 to 2.18.8 spans multiple minor releases and introduces significant changes, including a higher Java version requirement and new default processing limits that could break applications at runtime.

Key Changes:

• Java Version Requirement: The baseline Java version was raised to Java 8 starting with Jackson 2.14. Projects running on older Java versions must upgrade.
• New Processing Limits (v2.15+): To mitigate potential Denial of Service (DoS) attacks, default limits on input size have been introduced. Exceeding these may result in a StreamConstraintsException.
  • Maximum string value length: ~5 million characters
  • Maximum number value length: 1000 characters
  • Maximum nesting depth: 1000 levels
• Behavioral Changes:
  • v2.13: Coercion of JSON null to the Java String "null" in certain contexts is no longer performed, which was noted to break some downstream users.
  • v2.14: The behavior of JsonNode.with() and withArray() was changed to treat property names with a leading slash (/) as JSON Pointer expressions, which could affect code that uses such names literally.
  • v2.14: The precedence of @JsonIgnore over @JsonProperty was changed; @JsonIgnore now always wins, which could alter serialization output.
  • v2.17: Parsing of stringified numbers is stricter; for example, strings with leading zeroes like "07" are no longer coerced to numbers for Enum indexes.

Recommendation:

• Verify that your project's runtime is Java 8 or newer.
• Review if your application processes JSON documents that might exceed the new default processing limits. If so, you will need to configure the JsonFactory with custom StreamReadConstraints.
• Test thoroughly to ensure that the behavioral changes in property filtering, JSON Pointer handling, and type coercion do not negatively impact your application's logic.

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.