Skip to content

[Snyk] Security upgrade com.fasterxml.jackson.core:jackson-databind from 2.14.2 to 2.18.11 - #69

Open
caniszczyk wants to merge 1 commit into
masterfrom
snyk-fix-275480f10110f8ef7c42389ff8b84ca6
Open

caniszczyk wants to merge 1 commit into
masterfrom
snyk-fix-275480f10110f8ef7c42389ff8b84ca6

Conversation

@caniszczyk

Copy link
Copy Markdown

snyk-top-banner

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

Snyk changed the following file(s):

  • functions-framework-invoker/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-20059179
  828   com.fasterxml.jackson.core:jackson-databind:
2.14.2 -> 2.18.11
Proof of Concept
high severity Allocation of Resources Without Limits or Throttling
SNYK-JAVA-COMFASTERXMLJACKSONCORE-20059683
  721   com.fasterxml.jackson.core:jackson-databind:
2.14.2 -> 2.18.11
No Known Exploit

Breaking Change Risk

Merge Risk: Medium

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

@caniszczyk

Copy link
Copy Markdown
Author

Merge Risk: Medium

This upgrade from version 2.14.2 to 2.18.11 spans several minor versions and introduces significant new features and behavioral changes that require verification.

Potential Breaking Changes:

  • Processing Limits (from 2.15): The most critical change is the introduction of StreamReadConstraints to mitigate DoS vulnerabilities. New default limits are placed on properties like maximum string length (~20MB), nesting depth (1000), and numeric token length. Applications that process large or deeply nested JSON documents may encounter StreamConstraintsException where they previously worked.
  • Error Message Redaction (from 2.16): The default for StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION has been changed to false for security reasons. Error messages will now contain "REDACTED" instead of the source snippet, which may impact custom error parsing logic.
  • Internal Introspection Rewrite (in 2.18): A major internal rewrite of the POJO property introspection logic was performed. While this fixes many bugs, such a fundamental change could introduce subtle behavioral differences in complex serialization or deserialization scenarios.
  • Kotlin Version Support: Support for Kotlin versions below 1.8 has been dropped across these releases.

Recommendation:

  • Verify Processing Limits: Review if your application handles JSON documents that might exceed the new default constraints. If so, you will need to configure a custom StreamReadConstraints policy on your JsonFactory or ObjectMapper.
  • Review Error Handling: Check any code that relies on parsing source information from Jackson's exception messages.
  • Thorough Regression Testing: Due to the internal rewrite in version 2.18, it is crucial to perform thorough regression testing on your application's data binding logic, especially for complex models.

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

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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.

3 participants