1.4: Keep Jackson on 2.10.x: 2.10.5 with 2.10.5.1 databind #2684
Conversation
This file contains 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
barchetta
added
1.x
|
/trigger |
tomas-langer
force-pushed
the
1.4-jackson
branch
from
5deb2aa
to
de9f097
Compare
|
Rebased on latest 1.x to fix copyright issue |
romain-grecourt
approved these changes
Jan 27, 2021
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.
In 1.4.7 we had Jackson 2.10. This PR keeps us on 2.10 (instead of going to 2.11) for compatibility concerns.
This uses the latest version of Jackson 2.10 to address https://nvd.nist.gov/vuln/detail/CVE-2020-25649. To address this CVE Jackson released a new version of databind along with a new BOM. But left the rest of Jackson alone. So we end up with:
jackson-bom: 2.10.5.20201202
jackson-databind: 2.10.5.1
jackson-core, annotation and others: 2.10.5
Also see issue #2672 and #2566