CVE-2019-10173: Deserialization of Untrusted Data and Code Injection in xstream

CVE-2019-10173 · Severity: low · CVSS 3.1 · Published 2019-07-26

Deserialization of Untrusted Data and Code Injection in xstream

Technologies: com.thoughtworks.xstream:xstream (Maven). Vendors: Maven.

Quick answers

Is CVE-2019-10173 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-10173 being exploited in the wild.
How severe is CVE-2019-10173?
Low severity, with a CVSS score of 3.1, published 26 July 2019.
Which products and versions are affected?
com.thoughtworks.xstream:xstream (Maven) ECOSYSTEM:introduced=1.4.10,fixed=1.4.11.
Is there a fix for CVE-2019-10173?
Yes. com.thoughtworks.xstream:xstream (Maven): upgrade to 1.4.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-10173?
Check whether you run com.thoughtworks.xstream:xstream (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • com.thoughtworks.xstream:xstream (Maven): upgrade to 1.4.11 or later
    # set com.thoughtworks.xstream:xstream to 1.4.11 in your pom.xml or build.gradle

Affected products

  • com.thoughtworks.xstream:xstream (Maven) ECOSYSTEM:introduced=1.4.10,fixed=1.4.11

Identifiers

  • CVE-2019-10173
  • GHSA-hf23-9pf7-388p

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.