Skip to content

Update dependency com.fasterxml.jackson.core:jackson-databind to v2.13.4.2 [SECURITY]#108

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/maven-com.fasterxml.jackson.core-jackson-databind-vulnerability
Open

Update dependency com.fasterxml.jackson.core:jackson-databind to v2.13.4.2 [SECURITY]#108
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/maven-com.fasterxml.jackson.core-jackson-databind-vulnerability

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented Mar 12, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.fasterxml.jackson.core:jackson-databind (source) 2.13.2 -> 2.13.4.2 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2020-36518

jackson-databind is a data-binding package for the Jackson Data Processor. jackson-databind allows a Java stack overflow exception and denial of service via a large depth of nested objects.

CVE-2022-42004

In FasterXML jackson-databind before 2.12.7.1 and in 2.13.x before 2.13.4, resource exhaustion can occur because of a lack of a check in BeanDeserializer._deserializeFromArray to prevent use of deeply nested arrays. This issue can only happen when the UNWRAP_SINGLE_VALUE_ARRAYS feature is explicitly enabled.

CVE-2022-42003

In FasterXML jackson-databind 2.4.0-rc1 until 2.12.7.1 and in 2.13.x before 2.13.4.2 resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting, when the UNWRAP_SINGLE_VALUE_ARRAYS feature is enabled. This was patched in 2.12.7.1, 2.13.4.2, and 2.14.0.

Commits that introduced vulnerable code are
FasterXML/jackson-databind@d499f2e, FasterXML/jackson-databind@0e37a39, and FasterXML/jackson-databind@7ba9ac5.

Fix commits are FasterXML/jackson-databind@cd09097 and FasterXML/jackson-databind@d78d00e.

The 2.13.4.1 release does fix this issue, however it also references a non-existent jackson-bom which causes build failures for gradle users. See https://github.com/FasterXML/jackson-databind/issues/3627#issuecomment-1277957548 for details. This is fixed in 2.13.4.2 which is listed in the advisory metadata so that users are not subjected to unnecessary build failures


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/maven-com.fasterxml.jackson.core-jackson-databind-vulnerability branch from e31913b to 566358b Compare March 16, 2023 17:52
@renovate renovate bot changed the title Update dependency com.fasterxml.jackson.core:jackson-databind to v2.13.4.1 [SECURITY] Update dependency com.fasterxml.jackson.core:jackson-databind to v2.13.4.2 [SECURITY] Mar 16, 2023
@renovate renovate bot changed the title Update dependency com.fasterxml.jackson.core:jackson-databind to v2.13.4.2 [SECURITY] Update dependency com.fasterxml.jackson.core:jackson-databind to v2.13.4.1 [SECURITY] Mar 30, 2023
@renovate renovate bot force-pushed the renovate/maven-com.fasterxml.jackson.core-jackson-databind-vulnerability branch from 566358b to 147e2f4 Compare March 30, 2023 00:40
@renovate renovate bot changed the title Update dependency com.fasterxml.jackson.core:jackson-databind to v2.13.4.1 [SECURITY] Update dependency com.fasterxml.jackson.core:jackson-databind to v2.13.4.2 [SECURITY] Mar 31, 2023
@renovate renovate bot force-pushed the renovate/maven-com.fasterxml.jackson.core-jackson-databind-vulnerability branch from 147e2f4 to 30b534d Compare March 31, 2023 15:50
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.

0 participants