Patchfirst
CVE-2020-26259 Public exploit Medium · 6.8 EPSS 82.4%

XStream is vulnerable to an Arbitrary File Deletion on the local host when unmarshalling

x-stream · xstream

Summary

XStream, a Java library for serializing objects to XML and back, contains an arbitrary file deletion flaw during unmarshalling that affects versions before 1.4.15 and is reachable through the processed input stream. A remote attacker who can supply crafted input to an affected deserialization path can delete arbitrary files on the host, provided the executing process has sufficient rights and the attack is not possible on Java 15 or higher, nor where a whitelist-based Security Framework is configured.

Official description · CVE.org

XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.15, is vulnerable to an Arbitrary File Deletion on the local host when unmarshalling. The vulnerability may allow a remote attacker to delete arbitrary know files on the host as log as the executing process has sufficient rights 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.15. The reported vulnerability does not exist running Java 15 or higher. 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.14 or below who still want to use XStream default blacklist can use a workaround described in more detailed in the referenced advisories.

Breakdown
29.7 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15

Public exploit code (PoC-in-GitHub) was available 3 days before disclosure.

  1. Public exploit codePoC-in-GitHub3 days before
  2. Disclosedday 0

7 fixes in xstream over 20 months. The latest fix listed for xstream is 1.4.16.

Fixes in xstreamMaven package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 1.4.11CVE-2019-1017323 Jul 2019
  2. 1.4.14-java7CVE-2020-2621716 Nov 2020
  3. 1.4.15CVE-2020-2625816 Dec 2020
  4. 1.4.15CVE-2020-2625916 Dec 2020
  5. 1.4.16CVE-2021-2134122 Mar 2021
  6. 1.4.16CVE-2021-2134222 Mar 2021
  7. 1.4.16CVE-2021-2134322 Mar 2021Latest listed

techniques

No techniques linked

No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: com.thoughtworks.xstream:xstream.

Mavencom.thoughtworks.xstream:xstreamGHSA-jfvx-7wrx-43fh

Upgrade to 1.4.18 or later

Fixes this CVE and 12 other known vulnerabilities in this package (CVE-2013-7285, CVE-2019-10173, +10).

Set the version to 1.4.18 or later in your pom.xml or build.gradle.

First fixed in 1.4.15 for CVE-2020-26259.

Affected versions

If you runUpgrade to
All versions before 1.4.151.4.18first fix for this CVE: 1.4.15

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

References

9 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close