[Snyk] Security upgrade com.fasterxml.jackson.datatype:jackson-datatype-jsr310 from 2.15.3 to 2.18.6

[sajith-subramanian]

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

Snyk changed the following file(s):

• datamanagement/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-15365924	170	com.fasterxml.jackson.datatype:jackson-datatype-jsr310: 2.15.3 -> 2.18.6 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

[sajith-subramanian]

This upgrade from version 2.15.3 to 2.18.6 is a minor version update but includes several notable changes across the Jackson ecosystem that require attention.

Key Changes:

• Java Version Requirement: As of Jackson 2.17, the baseline Java requirement was raised to Java 8. Projects still on Java 7 will need to upgrade their JDK.
• Stricter Deserialization: In version 2.17, deserialization of numbers from strings with leading zeroes (e.g., "07") is no longer permitted by default for numeric types like Enum indexes.
• Exception Class Relocation: A significant change in the broader Jackson 2.17 release is the relocation of core exception classes like StreamReadException and StreamWriteException. They have moved from com.fasterxml.jackson.core.exc to the com.fasterxml.jackson.core package. While this change is in the jackson-core library, it affects any application code that directly catches these specific exceptions.

Recommendation:

• Verify that your project's runtime is Java 8 or newer.
• Review any custom error handling logic that catches Jackson's StreamReadException or StreamWriteException to ensure imports are updated to the new package.
• Test deserialization logic that relies on lenient parsing of numbers from strings, as the behavior is now stricter.

Source: Jackson 2.17 Release Notes

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

[Copilot]

Pull request overview

Updates the Data Management SDK module’s Jackson JSR-310 datatype dependency version to address a Snyk-reported Jackson-core vulnerability.

Changes:

• Bump jackson.version in datamanagement/pom.xml from 2.15.3 to 2.18.6.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Bumping jackson.version here upgrades jackson-datatype-jsr310, but this module also depends on com.autodesk.aps:sdkmanager, which currently pins jackson-databind to 2.15.3. That can lead to mixed Jackson versions (and Maven may still resolve jackson-core/jackson-databind to 2.15.3 due to dependency mediation), which both risks runtime linkage errors and may fail to actually remediate the reported Jackson-core vulnerability. Consider aligning all Jackson artifacts via dependencyManagement (e.g., importing the Jackson BOM) or updating/overriding sdkmanager’s Jackson version so the resolved jackson-core/jackson-databind versions match ${jackson.version}.