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

[caniszczyk]

Snyk has created this PR to fix 1 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
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-18517159	828	com.fasterxml.jackson.core:jackson-databind: 2.14.2 -> 2.18.8 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

[caniszczyk]

This upgrade of Jackson Databind from 2.14.2 to 2.18.8 is a minor version update that spans several releases. While there are no major API removals, there are significant behavioral changes and internal rewrites that require careful verification.

Key Changes and Potential Impacts:

• Processing Limits (since 2.15): New default limits have been introduced on the maximum size of processed tokens to prevent Denial of Service attacks. For example, the maximum string length defaults to 1 million characters and numeric token length to 1000 characters. Applications processing unusually large JSON values may encounter new exceptions.

• Security Default Change (since 2.16): The default for StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION has been changed to false. This prevents leaking source information in exceptions and is a security enhancement, but it may affect error handling logic that relied on this data.

• POJO Introspection Rewrite (in 2.18): Version 2.18 includes a complete rewrite of the POJO property introspection mechanism. While this fixes numerous long-standing bugs, such a significant internal change carries a risk of introducing subtle behavioral differences in serialization or deserialization, especially in complex object models.

• Kotlin Support (in 2.18): Support for Kotlin version 1.7.x has been dropped.

Recommendation:

Due to the introduction of processing limits and the major internal rewrite of property introspection, this upgrade carries a medium risk of introducing behavioral changes. It is critical to perform thorough regression testing, paying special attention to:

• Deserialization of large string or number values.
• Custom error handling logic.
• Complex object mapping, especially involving creators, naming strategies, or records.

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

[CLAassistant]

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.}