Skip to content
Fencer Vulns
high 7.3

CVE-2019-10173 in the critical feed json

Deserialization of Untrusted Data and Code Injection in xstream

published 2019-07-23 7 y ago modified 2026-09-10 1 mo ago also GHSA-hf23-9pf7-388p , EUVD-2019-0591

cvss
7.3
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
95.0%
EPSS 95.0% chance of exploitation in 30 days, percentile 99.8%
public exploits
0
none known

Summary

It was found that xstream API version 1.4.10 before 1.4.11 introduced a regression for a previous deserialization flaw. If the security framework has not been initialized, it may allow a remote attacker to run arbitrary shell commands when unmarshalling XML or any supported format. e.g. JSON. (regression of CVE-2013-7285)

Patch / fix

  • maven com.thoughtworks.xstream:xstream 1.4.11
  • libxstream-java Debian 14, Debian 13, Debian 12 1.4.11-1

debian advisories DEBIAN-CVE-2019-10173

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-10173 updated cvss 7.3

xstream: remote code execution due to insecure XML deserialization (regression of CVE-2013-7285)

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

95.04% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.0 7.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven com.thoughtworks.xstream:xstream
>=1.4.10, <1.4.11
1.4.11

Affected products

  • xstream xstream

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.