Skip to content

SWI-3723 [Snyk] Fix for 1 vulnerabilities#39

Open
bwappsec wants to merge 1 commit intomasterfrom
snyk-fix-60439cd8976431e411f72abcb2495347
Open

SWI-3723 [Snyk] Fix for 1 vulnerabilities#39
bwappsec wants to merge 1 commit intomasterfrom
snyk-fix-60439cd8976431e411f72abcb2495347

Conversation

@bwappsec
Copy link

@bwappsec bwappsec commented Mar 5, 2026

snyk-top-banner

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
high severity Allocation of Resources Without Limits or Throttling
SNYK-JAVA-COMFASTERXMLJACKSONCORE-15365924
  170   com.fasterxml.jackson.core:jackson-core:
2.9.5 -> 2.18.6
com.fasterxml.jackson.core:jackson-databind:
2.9.5 -> 2.18.6
com.fasterxml.jackson.dataformat:jackson-dataformat-xml:
2.9.4 -> 2.18.6
com.fasterxml.jackson.datatype:jackson-datatype-guava:
2.9.5 -> 2.18.6
com.fasterxml.jackson.datatype:jackson-datatype-jdk8:
2.8.6 -> 2.18.6
No Path Found Proof of Concept

Breaking Change Risk

Merge Risk: High

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

@bwappsec
Copy link
Author

bwappsec commented Mar 5, 2026

Merge Risk: High

This is a major upgrade for the Jackson suite, jumping from version 2.9.x to 2.18.6. This update spans numerous releases and introduces significant breaking changes, new features, and a higher Java baseline requirement.

Key Breaking Changes:

  • Java Version Requirement: The minimum Java version has been increased. jackson-databind requires Java 8 since version 2.13, and jackson-core requires Java 8 since version 2.14. Your project must be on Java 8 or later. [2, 5, 13]

  • Safe Default Typing (Polymorphic Deserialization): To address multiple security vulnerabilities (CVEs), version 2.10 introduced a new "Safe Default Typing" mechanism. The previous methods for enabling polymorphic typing are now considered unsafe and have been replaced. If your application uses this feature, you must migrate to the new activateDefaultTyping() methods to ensure security and functionality. [4]

  • Behavioral Changes:

    • Stricter Deserialization: Later versions have introduced stricter parsing rules. For example, in 2.17, strings with leading zeros (e.g., "07") are no longer automatically coerced into numbers. [1]
    • @JsonIgnore Precedence: As of version 2.14, @JsonIgnore is now consistently given priority over other annotations like @JsonProperty, which may cause fields to be unexpectedly excluded from serialization/deserialization. [13]
    • Null Handling: In version 2.13, Jackson stopped coercing a JSON null value into the literal string "null" in certain contexts, which may affect applications that relied on this behavior. [2]
  • Dependency Changes: The jackson-dataformat-xml module no longer has a direct dependency on jackson-module-jaxb-annotations as of version 2.13. [2, 6]

Recommendation:

Due to the number of breaking changes and the long span of versions, this upgrade requires careful testing and likely code modifications. Pay special attention to:

  1. Ensuring your environment uses Java 8 or newer.
  2. Updating any code that uses polymorphic type handling to the new "Safe Default Typing" APIs.
  3. Thoroughly testing your application's JSON/XML serialization and deserialization logic to catch any issues arising from the stricter parsing and behavioral changes.

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

@bwappsec
Copy link
Author

bwappsec commented Mar 5, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

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

@bwappsec bwappsec changed the title [Snyk] Fix for 1 vulnerabilities SWI-3723 [Snyk] Fix for 1 vulnerabilities Mar 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants