[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
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-18517159	169	com.fasterxml.jackson.core:jackson-core: 2.10.0 -> 2.18.8 com.fasterxml.jackson.core:jackson-databind: 2.10.0 -> 2.18.8 com.fasterxml.jackson.datatype:jackson-datatype-jsr310: 2.10.0 -> 2.18.8 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:

🦉 Allocation of Resources Without Limits or Throttling

[snyk-io]

This upgrade from Jackson 2.10.0 to 2.18.8 spans multiple versions and introduces several important changes, including new security defaults and behavioral modifications that require verification.

Key Changes and Potential Breaks:

• Java Version Requirement: Starting with version 2.14, jackson-core requires a Java 8 baseline. Applications running on older JDKs must be updated.

• New Security-Motivated Processing Limits: To mitigate denial-of-service (DoS) risks, version 2.15 introduced configurable processing limits. If your application handles very large or deeply nested JSON documents, you may encounter StreamConstraintsException. These limits are configurable but have new, safer defaults.

• Behavioral Change in Annotation Precedence: In version 2.14, the handling of @JsonIgnore was changed to give it higher precedence over @JsonProperty when used across a class hierarchy. This could alter which fields are included in the final JSON output and requires reviewing models with mixed annotations.

• Java Record Deserialization: Version 2.15 changed how Java Records are deserialized to align them with standard POJOs. This was a notable breaking change for applications that relied on the previous field-based deserialization behavior.

• jackson-datatype-jsr310 API Change: A breaking change was introduced in InstantDeserializer between versions 2.15 and 2.16, which may affect custom date/time handling.

• Default Behavior Change for Source Location: For security reasons, version 2.16 changed the default of StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION to false, which reduces the information available in error messages.

Recommendation:

Given the number of subtle behavioral changes and new defaults, thorough testing is essential. Pay close attention to:

1. Verifying your project uses Java 8 or newer.
2. Testing JSON processing pipelines that handle large or complex documents to ensure they do not hit the new default stream limits.
3. Reviewing data models that use Java Records or complex annotation hierarchies (@JsonIgnore/@JsonProperty) for any unexpected changes in serialization.

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. 14 issues have been found so far.

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

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