') call.">
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.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2017:2888 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2017:1832 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2017:2889 | third party advisory vendor advisory |
http://www.securitytracker.com/id/1039499 | vdb entry broken link third party advisory |
https://www-prd-trops.events.ibm.com/node/715749 | broken link permissions required |
https://exchange.xforce.ibmcloud.com/vulnerabilities/125800 | third party advisory vdb entry |
http://www.debian.org/security/2017/dsa-3841 | vendor advisory third party advisory mailing list |
http://x-stream.github.io/CVE-2017-7957.html | vendor advisory |
http://www.securityfocus.com/bid/100687 | vdb entry broken link third party advisory |