HighGHSA-jjjh-jjxp-wpffCVE-2022-42003

Uncontrolled Resource Consumption in Jackson-databind

Published 3 Oct 2022 · Updated 10 Sept 2026

Is your project on an affected com.fasterxml.jackson.core:jackson-databind?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=2.4.0-rc1 <2.12.7.1
Fixed in
2.12.7.1
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.12.7.1 -DforceVersion=true
Affected
>=2.13.0 <2.13.4.2
Fixed in
2.13.4.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.13.4.2 -DforceVersion=true

Details

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 https://github.com/FasterXML/jackson-databind/commit/d499f2e7bbc5ebd63af11e1f5cf1989fa323aa45, https://github.com/FasterXML/jackson-databind/commit/0e37a39502439ecbaa1a5b5188387c01bf7f7fa1, and https://github.com/FasterXML/jackson-databind/commit/7ba9ac5b87a9d6ac0d2815158ecbeb315ad4dcdc.

Fix commits are https://github.com/FasterXML/jackson-databind/commit/cd090979b7ea78c75e4de8a4aed04f7e9fa8deea and https://github.com/FasterXML/jackson-databind/commit/d78d00ee7b5245b93103fef3187f70543d67ca33.

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

Is GHSA-jjjh-jjxp-wpff in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected com.fasterxml.jackson.core:jackson-databind, and gives you the command that fixes it.

More advisories for com.fasterxml.jackson.core:jackson-databind

  • HighCVE-2026-91777jackson-databind quadratic forward-reference completion · 30 Sept 2026
  • HighCVE-2026-91776jackson-databind retains every unknown raw type ID · 30 Sept 2026
  • MediumCVE-2026-83557jackson-databind: Comparable missing from DefaultBaseTypeLimitingValidator's unsafe base types (incomplete PolymorphicTypeValidator denylist) · 28 Sept 2026
  • HighCVE-2026-68497jackson-databind: Duration XMLGregorianCalendar Unbounded Number Parse DoS · 28 Sept 2026
  • MediumCVE-2026-19032jackson-databind: Path Deserialization Missing Scheme Allowlist for FileSystemProvider Resolution · 28 Sept 2026
  • MediumCVE-2026-77310jackson-databind: Incomplete fix for CVE-2026-54514: eager DNS resolution (SSRF) still present in InetAddress deserialization · 28 Sept 2026
All 86 advisories for com.fasterxml.jackson.core:jackson-databind

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.