Skip to content

Uncontrolled Resource Consumption in Jackson-databind

High severity GitHub Reviewed Published Oct 3, 2022 to the GitHub Advisory Database • Updated Sep 13, 2024

Package

maven com.fasterxml.jackson.core:jackson-databind (Maven)

Affected versions

>= 2.4.0-rc1, < 2.12.7.1
>= 2.13.0, < 2.13.4.2

Patched versions

2.12.7.1
2.13.4.2

Description

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 FasterXML/jackson-databind#3627 (comment) 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

References

Published by the National Vulnerability Database Oct 2, 2022
Published to the GitHub Advisory Database Oct 3, 2022
Reviewed Oct 4, 2022
Last updated Sep 13, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.252%
(66th percentile)

Weaknesses

CVE ID

CVE-2022-42003

GHSA ID

GHSA-jjjh-jjxp-wpff

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.