LiveActive security incident?Get immediate response
CVE Record

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

FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.oracle.wls.shaded.org.apache.xalan.lib.sql.JNDIConnectionPool (aka embedded Xalan in org.glassfish.web/javax.servlet.jsp.jstl).

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. Affected Java applications may be at risk when older jackson-databind 2.x versions process untrusted typed data with specific gadget classes available. The public record does not show CISA KEV listing or confirmed active exploitation.

Executive priority

Prioritize remediation in externally reachable Java services and vendor products processing untrusted data. This is high impact but has high attack complexity and no cited active exploitation, so handle through accelerated patch management rather than crisis response.

Technical view

CVE-2020-35728 is a CWE-502 issue in FasterXML jackson-databind 2.x before 2.9.10.8 involving serialization gadgets and typing, specifically JNDIConnectionPool in embedded Xalan variants. CVSS 3.1 is 8.1, with network attack vector, no privileges, no user interaction, and high complexity.

Likely exposure

Exposure is most likely in Java services or downstream products bundling jackson-databind 2.x before 2.9.10.8, especially where untrusted JSON uses polymorphic typing and the named gadget is present. The CVE bundle lists affected vendor/product as n/a, so product-specific exposure needs local inventory and vendor advisories.

Exploitation context

The CVSS vector allows unauthenticated network exploitation, but attack complexity is high. The bundle marks KEV as false and provides no source confirming exploitation in the wild. Treat this as serious dependency risk, not as a proven actively exploited emergency.

Researcher notes

Key uncertainty is environmental exploitability: vulnerable version alone may not be enough without unsafe typing behavior and the relevant gadget on the classpath. The CVE source names jackson-databind before 2.9.10.8 and downstream advisories, but does not provide complete affected product enumeration.

Mitigation direction

  • Upgrade jackson-databind to 2.9.10.8 or a vendor-supported fixed release.
  • Apply relevant Debian, Oracle, NetApp, or application vendor security updates.
  • Prioritize internet-facing services that deserialize untrusted JSON data.
  • Review vendor guidance before changing runtime typing behavior.
  • Track bundled copies inside shaded or embedded Java dependencies.

Validation and detection

  • Inventory jackson-databind versions across applications, containers, and SBOMs.
  • Flag any 2.x version earlier than 2.9.10.8.
  • Check whether affected applications deserialize untrusted typed JSON.
  • Review classpaths for the named embedded Xalan gadget package.
  • Confirm vendor advisories cover each downstream product or appliance.
Prepared
Confidence
medium
Sources
6

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-35728 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
11Source 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-35728Attack 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.