[Snyk] Fix for 1 vulnerabilities

[kharshriya]

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

Snyk changed the following file(s):

• parent/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-15365924	828	com.fasterxml.jackson.core:jackson-core: 2.13.4 -> 2.18.6 com.fasterxml.jackson.core:jackson-databind: 2.13.4 -> 2.18.6 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

[kharshriya]

This upgrade moves jackson-core and jackson-databind from version 2.13.4 to 2.18.6. While this is a minor version upgrade, it includes several notable changes and new default behaviors that require verification.

Key Changes:

• Java 8 Baseline: Starting with version 2.14, jackson-core requires Java 8 or higher. [1, 3]
• Android SDK Requirement: The minimum Android SDK version required is now 26, starting from version 2.14. [3]
• Annotation Precedence Change: In version 2.14, the behavior for conflicting annotations was changed. @JsonIgnore now takes precedence over @JsonProperty, which could alter serialization or deserialization behavior for properties with both annotations. [3]
• JsonNode Behavior Change: The JsonNode.with() and withArray() methods in version 2.14 now interpret arguments with a leading forward slash (/) as JSON Pointer expressions. This may affect code that uses these methods with property names containing slashes. [3]
• New Processing Limits: To mitigate potential DoS attacks, version 2.15 introduced StreamReadConstraints with default limits on maximum string length, number token length, and nesting depth (default 1000). [12, 13] Applications processing very large or deeply nested JSON may need to adjust these constraints.
• Stricter Number Coercion: As of version 2.17, Jackson is stricter when coercing numbers from strings. For example, a JSON string like "07" will no longer be recognized as a valid number for an Enum index. [24]

Recommendation:

Review your project for reliance on the previous behaviors, especially concerning annotation precedence and JsonNode.with() usage. It is also important to verify that your application's JSON payloads do not exceed the new default processing limits.

Source: Jackson Release Notes

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