LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11113: FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and...

FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.openjpa.ee.WASRegistryManagedRuntime (aka openjpa).

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a high-severity Jackson databind deserialization issue. A vulnerable application may be at risk if it uses jackson-databind before 2.9.10.4 with risky typing behavior and the OpenJPA-related gadget class available. The bundle does not show active exploitation.

Executive priority

Prioritize remediation for externally reachable Java applications and vendor products that embed Jackson. This is high severity, but urgency depends on exposed JSON inputs, typing configuration, and the relevant gadget class being present.

Technical view

CVE-2020-11113 is CWE-502 in FasterXML jackson-databind 2.x before 2.9.10.4. It concerns interaction between serialization gadgets and typing, specifically org.apache.openjpa.ee.WASRegistryManagedRuntime. CVSS 3.1 is 8.8, network reachable, low complexity, no privileges, user interaction required.

Likely exposure

Most likely exposure is Java software that embeds vulnerable jackson-databind and processes attacker-influenced JSON with unsafe polymorphic typing. Exposure also depends on whether the OpenJPA gadget class is present. The provided affected-product data is incomplete and lists no concrete vendor product CPEs.

Exploitation context

The CVSS vector indicates remote attack potential with low complexity and no privileges, but user interaction is required. KEV is false, and the provided bundle does not cite confirmed active exploitation. Treat exploitability as configuration and classpath dependent, not automatic for every Jackson user.

Researcher notes

The source bundle identifies the vulnerable library and gadget relationship, but does not provide full affected downstream product versions. Validate exposure through dependency, classpath, and deserialization configuration analysis. Do not assume every jackson-databind deployment is exploitable.

Mitigation direction

  • Upgrade jackson-databind to 2.9.10.4 or a vendor-supported fixed release.
  • Review Debian, Oracle, NetApp, and upstream guidance for packaged or embedded copies.
  • Disable or restrict unsafe polymorphic typing where application design permits.
  • Inventory Java dependencies for transitive jackson-databind and OpenJPA exposure.
  • Prioritize internet-facing services that parse untrusted JSON.

Validation and detection

  • Check dependency manifests and runtime SBOMs for jackson-databind versions before 2.9.10.4.
  • Confirm whether OpenJPA classes are present on affected application classpaths.
  • Review code for default typing or broad polymorphic deserialization of untrusted data.
  • Verify patched packages against vendor advisories and deployed artifact versions.
  • Run regression tests covering JSON parsing paths after upgrading.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-11113 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2020-11113Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.