XStream API CVE-2019-10173 Deserialization Remote Code Execution Vulnerability

ID SMNTC-110969
Type symantec
Reporter Symantec Security Response
Modified 2019-07-23T00:00:00



XStream API is prone to a remote code-execution vulnerability. Successfully exploiting this issue may allow an attacker to execute arbitrary commands in the context of the affected application. Xstream API versions 1.4.10 is vulnerable.

Technologies Affected

  • IBM QRadar 7.3.0
  • IBM QRadar 7.3.0 Patch 1
  • IBM QRadar 7.3.0 Patch 5
  • IBM QRadar 7.3.0 Patch 6
  • IBM QRadar 7.3.0 Patch 7
  • IBM QRadar 7.3.1 Patch 4
  • IBM QRadar 7.3.1 Patch 5
  • IBM QRadar 7.3.1 Patch 8
  • IBM QRadar 7.3.2 Patch 1
  • IBM QRadar 7.3.2 Patch 4
  • Redhat JBoss Data Grid 7
  • Redhat JBoss Fuse 6.0
  • Redhat JBoss Fuse 7.0
  • Redhat JBoss Middleware Text-Only Advisories for MIDDLEWARE 1
  • Redhat Single Sign-On 7.0
  • XStream XStream 1.4.10
  • XStream XStream 1.4.8
  • XStream XStream 1.4.9


Block external access at the network boundary, unless external parties require service.
If global access isn't needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of a successful exploit.

Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of latent vulnerabilities, run the application with the minimal amount of privileges required for functionality

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity including unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploit

Implement multiple redundant layers of security.
Various memory-protection schemes (such as nonexecutable and randomly mapped memory segments) may hinder an attacker's ability to exploit this vulnerability to execute arbitrary code.

Reportedly, the issue is fixed; however, Symantec has not confirmed this. Please contact the vendor for more information.