fix(security): force jackson-databind 2.15.4 (CVE chain)#166
Open
devin-ai-integration[bot] wants to merge 1 commit intoDevOpsfrom
Open
fix(security): force jackson-databind 2.15.4 (CVE chain)#166devin-ai-integration[bot] wants to merge 1 commit intoDevOpsfrom
devin-ai-integration[bot] wants to merge 1 commit intoDevOpsfrom
Conversation
Co-Authored-By: Achal Channarasappa <achal.channarasappa@cognition.ai>
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Pins
com.fasterxml.jackson.core:jackson-databindto2.15.4via a new<dependencyManagement>block in the rootpom.xmlso transitive resolution cannot downgrade to vulnerable 2.13.x versions.jackson-databindis pulled transitively and can resolve to vulnerable 2.13.x versions exposed to a known deserialization CVE chain.jackson-databindto the latest 2.15.x patch (2.15.4) at the root POM so Maven's nearest-wins rule is overridden bydependencyManagement, preventing any transitive downgrade.Verification
mvn -DskipTests -B dependency:tree -Dverbose | grep jacksonconfirms 2.15.4 wins over the Spring Boot 3.3.3 managed 2.17.2:Review & Testing Checklist for Human
DevOpsbecause the repo has nomainbranch (default branch isDevOps). Confirm this is acceptable — the orchestrator directive saidmain.jackson-databindis now2.15.4whilejackson-coreandjackson-annotationsremain at2.17.2(Spring Boot 3.3.3 managed). Jackson generally supports minor-version mixing, but this is worth a smoke test of any JSON (de)serialization paths in the app.2.15.4actually remediates the intended CVE chain and isn't a regression vs. the previously-resolved2.17.2. If the concern is only about transitive downgrades to 2.13.x, bumping the pin to the latest 2.17.x may be preferable.docker-compose up) and exercise a login + a transaction to confirm no Jackson-related runtime errors.Notes
pom.xmlper the finding.Link to Devin session: https://app.devin.ai/sessions/f667d4386ac14b3684d1e5bf7379e074
Requested by: @achalc