LiveActive security incident?Get immediate response
CVE Record

CVE-2017-15095: A deserialization flaw was discovered in the jackson-databind in versions before 2.8.10 and 2.9.1, which co...

A deserialization flaw was discovered in the jackson-databind in versions before 2.8.10 and 2.9.1, which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper. This issue extends the previous flaw CVE-2017-7525 by blacklisting more classes that could be used maliciously.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-15095 is a Jackson databind deserialization issue that could let an unauthenticated attacker run code if a vulnerable Java application processes crafted input through ObjectMapper.readValue. The main business risk is legacy Java services still carrying old jackson-databind versions in application or vendor packages.

Executive priority

Prioritize remediation for internet-facing or partner-facing Java services first. Treat unknown ownership or bundled dependencies as a discovery problem, because older vulnerable libraries can remain inside application packages after OS patching.

Technical view

The flaw affects FasterXML jackson-databind before 2.8.10 and before 2.9.1. The CVE describes code execution via crafted input passed to ObjectMapper.readValue. It is tied to CWE-184 and extends CVE-2017-7525 by adding more classes to the denylist. The supplied bundle does not include CVSS scoring.

Likely exposure

Exposure is most likely in Java applications or downstream Red Hat/Debian packages using vulnerable jackson-databind versions, especially where untrusted client input reaches ObjectMapper.readValue. The bundle does not identify specific applications beyond FasterXML jackson-databind and vendor advisories.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. The vulnerability is still serious because the described outcome is unauthenticated code execution when vulnerable deserialization paths are reachable.

Researcher notes

Evidence is limited to the CVE description and vendor advisory references. The bundle supports affected versions, potential unauthenticated code execution, CWE-184, and relationship to CVE-2017-7525. It does not provide CVSS, proof of exploitation, or detailed product impact beyond jackson-databind and downstream advisories.

Mitigation direction

  • Upgrade jackson-databind to 2.8.10, 2.9.1, or a later supported fixed version.
  • Apply relevant Red Hat or Debian security updates where jackson-databind is OS-vendor supplied.
  • Remove or replace bundled vulnerable jackson-databind copies in application artifacts.
  • Review vendor guidance before relying on compensating controls.

Validation and detection

  • Inventory jackson-databind versions across SBOMs, lockfiles, build files, and deployed artifacts.
  • Confirm no runtime classpath loads jackson-databind before 2.8.10 or before 2.9.1.
  • Identify services where untrusted input reaches ObjectMapper.readValue.
  • Verify vendor package advisories are applied on affected Red Hat or Debian systems.
Prepared
Confidence
medium
Sources
6

Public sources used

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 · low confidence lookup

CWE-184: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-15095 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
28Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
FasterXMLjackson-databindbefore 2.8.10, before 2.9.1Listed
Weakness

CWE details

CWE-184

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

CWE-184 · source CWE mapping

Incomplete List of Disallowed Inputs

Incomplete List of Disallowed Inputs represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs