XStream void Type Unmarshalling Denial of Service
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.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
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.
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.
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.
No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.