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

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-19496766	147	com.fasterxml.jackson.core:jackson-databind: 2.10.0 -> 2.18.10 com.fasterxml.jackson.datatype:jackson-datatype-jsr310: 2.10.0 -> 2.18.10 No Path Found Proof of Concept

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:

🦉 Deserialization of Untrusted Data

[snyk-io]

This upgrade from version 2.10.0 to 2.18.10 for Jackson databind and JSR310 introduces a higher Java version requirement and new processing limits that could impact applications.

Key Changes:

• Java Version Requirement: The baseline Java version has been raised. jackson-databind requires Java 8 since version 2.13, and jackson-core requires Java 8 since version 2.14. [6, 7, 8]
• Processing Limits for DoS Protection: To mitigate security risks, versions 2.14 and 2.15 introduced default limits on input size. Exceeding these will result in a StreamConstraintsException. [1, 4]
  • Maximum numeric value length: 1,000 characters. [1]
  • Maximum document nesting depth: 1,000 levels. [1]
  • Maximum string value length: Initially 5 million characters, later increased. [4, 12]
• Stricter Parsing Behavior: Starting in version 2.17, JSON strings with leading zeros (e.g., "07") are no longer automatically converted to numbers for contexts like Enum indexes. [2]
• Javax to Jakarta Namespace: Version 2.13 introduced new modules for the jakarta.* namespace, which may require dependency adjustments if you use related Java EE APIs like JAXB. [6]

Recommendation:

• Ensure your runtime environment is Java 8 or newer.
• Test applications that process large or deeply nested JSON documents to verify they do not exceed the new default processing limits. These limits can be configured on the JsonFactory

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.