Fix CVE for Spark-3.4 #14748
Open
Fix CVE for Spark-3.4 #14748
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nastra
reviewed
Dec 4, 2025
| force "com.fasterxml.jackson.module:jackson-module-scala_${scalaVersion}:${libs.versions.jackson214.get()}" | ||
| force "com.fasterxml.jackson.core:jackson-databind:${libs.versions.jackson214.get()}" | ||
| force "com.fasterxml.jackson.core:jackson-core:${libs.versions.jackson214.get()}" | ||
| force "com.fasterxml.jackson.module:jackson-module-scala_${scalaVersion}:${libs.versions.jackson215.get()}" |
Contributor
There was a problem hiding this comment.
Spark 3.4 depends on jackson 2.14 as can be seen in https://github.com/apache/spark/blob/branch-3.4/pom.xml#L187-L188. Switching to jackson 2.15 can have side-effects and cause issues. What about addressing the CVE in Spark 3.4 first?
Member
There was a problem hiding this comment.
Spark no longer maintains 3.4.x and we've already decided to deprecate Spark 3.4 support. We might remove it in the next release so I think we can just leave it as is.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Impact :
With older versions of jackson-core, if you parse an input file and it has deeply nested data, Jackson could end up throwing a StackoverflowError if the depth is particularly large.
Patches :
jackson-core 2.15.0 contains a configurable limit for how deep Jackson will traverse in an input document, defaulting to an allowable depth of 1000. Change is in FasterXML/jackson-core#943. jackson-core will throw a StreamConstraintsException if the limit is reached.
jackson-databind also benefits from this change because it uses jackson-core to parse JSON inputs.