hadoop-fips-3.3.6
Chainguard
XStream can be used for Remote Code Execution
The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream.
If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.14.
No user is affected, who followed the recommendation to setup XStream's Security Framework with a whitelist! Anyone relying on XStream's default blacklist can immediately switch to a whilelist for the allowed types to avoid the vulnerability.
Users of XStream 1.4.13 or below who still want to use XStream default blacklist can use a workaround depending on their version in use.
Users of XStream 1.4.13 can simply add two lines to XStream's setup code:
Users of XStream 1.4.12 to 1.4.7 who want to use XStream with a black list will have to setup such a list from scratch and deny at least the following types: javax.imageio.ImageIO$ContainsFilter, java.beans.EventHandler, java.lang.ProcessBuilder, java.lang.Void and void.
Users of XStream 1.4.6 or below can register an own converter to prevent the unmarshalling of the currently know critical types of the Java runtime. It is in fact an updated version of the workaround for CVE-2013-7285:
Chen L found and reported the issue to XStream and provided the required information to reproduce it. He was supported by Zhihong Tian and Hui Lu, both from Guangzhou University.
See full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for CVE-2020-26217.
If you have any questions or comments about this advisory: