LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11111: 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.activemq.* (aka activemq-jms, activemq-core, activemq-pool, and activemq-pool-jms).

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 issue in Java applications. Older 2.x versions before 2.9.10.4 can mishandle dangerous serialization gadget classes tied to Apache ActiveMQ when typing is enabled. Successful exploitation could affect confidentiality, integrity, and availability, but exposure depends on application configuration and classpath.

Executive priority

Treat as a high-priority dependency remediation item for Java estates, not a confirmed emergency exploitation event. Focus first on externally exposed services and vendor products that bundle Jackson or ActiveMQ components.

Technical view

CVE-2020-11111 is a CWE-502 deserialization issue in FasterXML jackson-databind 2.x before 2.9.10.4. It concerns interaction between polymorphic typing and org.apache.activemq.* gadget classes, including activemq-jms, activemq-core, activemq-pool, and activemq-pool-jms. CVSS 3.1 is 8.8 with network attack vector, low complexity, no privileges, and user interaction required.

Likely exposure

Likely exposure is Java services using jackson-databind 2.x before 2.9.10.4, especially through transitive dependencies, with relevant ActiveMQ classes present and Jackson typing features processing untrusted data. The source bundle does not provide a complete affected product list.

Exploitation context

The bundle marks this CVE as not in KEV, and no provided source states active exploitation. Practical risk is configuration-dependent: vulnerable versions, unsafe typing behavior, reachable untrusted input, and gadget classes must align. The CVSS vector still indicates high potential impact.

Researcher notes

Evidence supports jackson-databind before 2.9.10.4 and ActiveMQ-related gadget classes. The affected CPE list is empty in the bundle, so product-level exposure requires dependency analysis. Do not assume every Jackson deployment is exploitable without confirming typing behavior, reachable input, and classpath conditions.

Mitigation direction

  • Upgrade jackson-databind to 2.9.10.4 or a later supported release.
  • Check vendor advisories for packaged products embedding jackson-databind.
  • Remove unnecessary ActiveMQ libraries from exposed application classpaths.
  • Avoid Jackson polymorphic typing for untrusted data where possible.
  • Apply Debian, Oracle, NetApp, or product-specific security updates when applicable.

Validation and detection

  • Inventory direct and transitive jackson-databind versions across Java applications.
  • Confirm whether affected services include org.apache.activemq.* libraries.
  • Review Jackson configuration for polymorphic or default typing on untrusted input.
  • Check whether vendor appliances or middleware list this CVE in advisories.
  • Prioritize internet-facing or externally fed deserialization paths.
Prepared
Confidence
high
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-11111 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-11111Attack 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.