dbcve.org
FuseApplication · Redhat

CVE-2017-7957

HIGH · 7.5 CVSS v3.1 Published 2017-04-29
Fix available
A fix is available. Upgrade to after 1.4.9 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
XStream through 1.4.9, when a certain denyTypes workaround is not used, mishandles attempts to create an instance of the primitive type 'void' during unmarshalling, leading to a remote application crash, as demonstrated by an xstream.fromXML("<void/>") call.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

XStream through version 1.4.9 contains a vulnerability during XML unmarshalling where attempting to deserialize the primitive type 'void' (e.g., via xstream.fromXML('<void/>')) causes an application crash due to improper instantiation handling of this special type.

MitigationUpgrade to XStream 1.4.10 or later where the issue is resolved, or implement the denyTypes workaround to block void type deserialization as a temporary mitigation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FuseApplication
Affected:= 1.0
Jboss MiddlewareApplication
Affected:= 1
Debian LinuxOperating system
Affected:= 8.0= 9.0
XstreamApplication
Affected:<= 1.4.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify XStream library version
    Search for xstream JAR files in your application dependencies or classpath (e.g., in WEB-INF/lib, lib directories, or Maven/Gradle dependencies). Check the filename or manifest for version 1.4.x or 1.4.9
    Affected if XStream version is 1.4.9 or earlier (1.4.x <= 1.4.9)
  2. Verify XStream is used for XML unmarshalling
    Search your codebase for calls to XStream.fromXML(), xstream.fromXML(), or similar unmarshalling methods that parse XML input
    Affected if Your code calls fromXML() to deserialize XML data into objects
  3. Determine if XML input is untrusted or user-controlled
    Inspect the source of XML data: check if fromXML() receives data from HTTP requests, file uploads, external APIs, message queues, or other untrusted sources
    Affected if XML data passed to fromXML() originates from untrusted or external sources (e.g., user uploads, network requests, deserialized data)
  4. Search for void element in XML processing logic
    Review any XML schemas, validators, or whitelists that filter XML content before passing to XStream; check if <void/> elements could reach the unmarshaller
    Affected if The application processes XML that could contain or be manipulated to contain <void/> elements
  5. Check Red Hat or Debian specific package versions
    If using packaged software (Red Hat Fuse, Red Hat JBoss Middleware, Debian Linux), query the installed package version using rpm -q or dpkg -l for xstream or related xml libraries
    Affected if Running Debian 8.0/9.0, Red Hat Fuse 1.0, or Red Hat JBoss Middleware version 1 with vulnerable XStream bundled

You are affected if XStream version 1.4.9 or earlier is in use AND your application deserializes untrusted or user-controlled XML via fromXML() which could include a <void/> element.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.4.9
Interim mitigation

Upgrade to XStream 1.4.10 or later where the issue is resolved, or implement the denyTypes workaround to block void type deserialization as a temporary mitigation.

Fix this in Fuse Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7957 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-7957 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data