Skip to main content
Mallory
HighVulnerability

CVE-2017-7957: XStream void Type Unmarshalling Denial of Service

Published Apr 29, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS4.9%92nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Debian ProjectRed HatXstream
IdentifiersCVE-2017-7957CWE-20 · Improper Input Validation

CVE-2017-7957 is an improper input validation vulnerability in XStream through version 1.4.9. When unmarshalling attacker-controlled XML type information, XStream can mishandle an attempt to instantiate the primitive void type. Because void cannot have an instance, a crafted input such as a void element can cause the consuming application to crash. The issue is avoided when the applicable denyTypes workaround is configured.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote unauthenticated attacker able to supply serialized XStream input can terminate the affected application, resulting in denial of service. Confidentiality and integrity impact are not described.

Mitigation

If you can’t patch tonight, do this now.

Configure XStream's applicable denyTypes protection to reject the primitive void type, and do not unmarshal untrusted XML or attacker-controlled serialized data. Restrict access to interfaces that accept XStream input where processing untrusted input cannot be avoided.

Remediation

Patch, then assume compromise.

Apply the vendor-provided security update for the affected XStream-dependent product. Red Hat addressed the issue in JBoss Fuse/A-MQ 6.3 through RHSA-2017:1832, JBoss BRMS 6.4 through RHSA-2017:2888, and JBoss BPM Suite 6.4 through RHSA-2017:2889. Verify installed package build versions rather than relying solely on upstream version strings, as fixes may be backported.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Debian ProjectDebian Linuxoperating_system
Red HatJboss Fuseapplication
Red HatJboss Middlewareapplication
XstreamXstreamapplication
FAQ

Frequently asked questions

Is CVE-2017-7957 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2017-7957 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2017-7957?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2017-7957.
Is there a patch for CVE-2017-7957?
Apply the vendor-provided security update for the affected XStream-dependent product. Red Hat addressed the issue in JBoss Fuse/A-MQ 6.3 through RHSA-2017:1832, JBoss BRMS 6.4 through RHSA-2017:2888, and JBoss BPM Suite 6.4 through RHSA-2017:2889.
What products are affected by CVE-2017-7957?
Xstream, Debian Project Debian Linux, Red Hat Jboss Fuse, and Red Hat Jboss Middleware.
How severe is CVE-2017-7957?
CVE-2017-7957 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 4.9% (92nd percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.