LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11112: 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.commons.proxy.provider.remoting.RmiProvider (aka apache/commons-proxy).

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-11112 is a high-severity Jackson databind deserialization issue. In affected 2.x versions before 2.9.10.4, certain typing behavior can interact badly with a serialization gadget from apache/commons-proxy. If reachable in an application, impact could include confidentiality, integrity, and availability compromise.

Executive priority

Treat as a high-priority dependency remediation item for Java estates, especially exposed services. It is not confirmed actively exploited in the provided sources, but the potential impact is broad enough to justify prompt inventory and patch tracking.

Technical view

The issue is classified as CWE-502 and has CVSS 3.1 score 8.8: network attack vector, low complexity, no privileges, user interaction required, and high CIA impact. The named gadget is org.apache.commons.proxy.provider.remoting.RmiProvider, related to apache/commons-proxy.

Likely exposure

Likely exposure is Java software using FasterXML jackson-databind 2.x before 2.9.10.4, especially where the referenced commons-proxy class is present. The bundle does not provide CPEs or exact downstream affected versions, so dependency inventory is required.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Risk remains meaningful because the CVSS vector indicates remote reachability, low complexity, no privileges, and high potential impact when the vulnerable conditions exist.

Researcher notes

Evidence identifies the vulnerable component and gadget class but lacks precise CPEs, exploit status, and product-specific applicability. Validate exposure by dependency graph, runtime classpath, Jackson configuration, and downstream vendor advisories rather than assuming every Jackson use is exploitable.

Mitigation direction

  • Upgrade jackson-databind to 2.9.10.4 or a vendor-supported fixed version.
  • Check Debian, Oracle, NetApp, and application vendor advisories for packaged fixes.
  • Inventory transitive jackson-databind and commons-proxy dependencies in Java applications.
  • Review application typing/deserialization configuration against current Jackson guidance.
  • Prioritize internet-facing or externally supplied data paths first.

Validation and detection

  • Confirm deployed jackson-databind versions are not before 2.9.10.4.
  • Check whether apache/commons-proxy is present in application classpaths.
  • Identify services that deserialize externally supplied data with Jackson typing features.
  • Review vendor product matrices for Oracle, NetApp, and OS package exposure.
  • Verify remediation through dependency scans and runtime software inventory.
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-11112 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-11112Attack 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.