dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-42004

HIGH · 7.5 CVSS v3.1 Published 2022-10-02
Fix available
A fix is available. Upgrade to 2.12.7.1 / 2.13.0 or later.
See remediation →
84/100
Remediation priority · High
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In FasterXML jackson-databind 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. An application is vulnerable only with certain customized choices for deserialization.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-502

The application rebuilds objects from attacker-supplied serialized data, and the act of rebuilding can trigger dangerous code paths. In many runtimes this leads straight to remote code execution. The durable fix is to avoid deserializing untrusted input — or to use a strict, type-limited format with integrity checks.

General guidance for the deserialization of untrusted data class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 10.0= 11.0
Jackson DatabindApplication
Affected:< 2.12.7.1>= 2.13.0, < 2.13.4
QuarkusApplication
Affected:< 2.13.0
Oncommand Workflow AutomationApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.12.7.1 / 2.13.0 / 2.13.4 or later
Fixed in 2.12.7.12.13.02.13.4
Vendor patch bugs.chromium.org →
Recommended fix High confidence

Jackson Databind 2.12.7.1 or 2.13.4+ (or Quarkus 2.13.0+)

  1. 1. Identify all Java applications in your environment that use FasterXML Jackson Databind library
  2. 2. For each application, determine the current Jackson Databind version in use (check pom.xml, build.gradle, or manifest files)
  3. 3. If using Jackson Databind version < 2.12.7.1 or >= 2.13.0 but < 2.13.4, upgrade to version 2.12.7.1 or 2.13.4 or later
  4. 4. If using Quarkus, upgrade to version 2.13.0 or later which includes the fixed Jackson Databind
  5. 5. Rebuild and redeploy all affected applications
  6. 6. Verify the upgrade by checking that the new Jackson Databind version is loaded at runtime
  7. 7. Test application functionality to ensure deserialization still works correctly with your custom configurations
Caveat Minimal risk; this is a security fix for a specific deeply nested array deserialization edge case; review custom deserializers for potential impact

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42004 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-42004 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data