LiveActive security incident?Get immediate response
CVE Record

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

FasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to oracle.jms.AQjmsQueueConnectionFactory, oracle.jms.AQjmsXATopicConnectionFactory, oracle.jms.AQjmsTopicConnectionFactory, oracle.jms.AQjmsXAQueueConnectionFactory, and oracle.jms.AQjmsXAConnectionFactory (aka weblogic/oracle-aqjms).

HighCVSS 8.1Not 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. Applications using vulnerable 2.x versions before 2.9.10.5 may be exposed when unsafe typing interacts with specific Oracle AQJMS/WebLogic gadget classes. The business risk is compromise of confidentiality, integrity, and availability, but exploitation conditions are not trivial.

Executive priority

Treat as a high-priority dependency remediation item for Java estates, especially externally reachable services. Prioritize inventory and upgrade planning over emergency response unless local evidence shows risky typing and gadget exposure.

Technical view

CVE-2020-14061 is CWE-502 in FasterXML jackson-databind 2.x before 2.9.10.5. It concerns mishandling between serialization gadgets and typing involving oracle.jms AQjms connection factory classes. CVSS 3.1 is 8.1 with network attack vector, no privileges, no user interaction, and high impact, but high attack complexity.

Likely exposure

Exposure is most likely in Java services that include jackson-databind before 2.9.10.5 and use risky polymorphic typing with reachable Oracle AQJMS/WebLogic classes. The provided CVE affected-product fields are incomplete, so dependency inventory matters.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates remote, unauthenticated potential, but high attack complexity and gadget/type conditions limit automatic exposure assumptions.

Researcher notes

The key validation question is not only version presence, but whether vulnerable databind behavior combines with reachable Oracle AQJMS/WebLogic gadget classes and unsafe typing. Public source data does not prove exploitation in the wild.

Mitigation direction

  • Inventory all applications and libraries using jackson-databind 2.x.
  • Upgrade jackson-databind to 2.9.10.5 or a vendor-supported fixed release.
  • Apply distribution or product advisories from Debian, Oracle, NetApp, or relevant vendors.
  • Review use of polymorphic typing and remove unsafe deserialization patterns where feasible.
  • Check whether Oracle AQJMS/WebLogic classes are present in vulnerable application classpaths.

Validation and detection

  • Confirm resolved jackson-databind versions in build locks and runtime artifacts.
  • Search dependency trees for jackson-databind versions earlier than 2.9.10.5.
  • Review application configuration for enabled default or polymorphic typing.
  • Verify vendor appliances or bundled Java products against referenced advisories.
  • Document compensating controls if immediate upgrade is blocked.
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-14061 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.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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
10Source 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.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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.