CVE-2020-26258mediumCWE-918

Server-Side Forgery Request can be activated unmarshalling with XStream

50Vexday Risk Score

Patch soon. It has a working public exploit.

ssvc Attendcvss 6.3epss 82%

exploitation probability

82%top 1% of all CVEs

observed exploitation

nono source reports it

What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Red HatVEX document ↗

Affected

11 products (13 components)

Red Hat Enterprise Linux 7 · Red Hat BPM Suite 6 · Red Hat Integration Camel K 1 · Red Hat Integration Camel Quarkus 1 · Red Hat JBoss A-MQ 6 · and others 6

workaround: As recommended, use XStream's security framework to implement a whitelist for the allowed types. Users of XStream 1.4.14 who insist to use XStream default blacklist - despite that clear recommendation - can simply add two lines to XStream's setup…

Fixed

6 products

RHDM 7.11.0 · RHPAM 7.11.0 · Red Hat Data Grid 8.2.0 · Red Hat Fuse 7.9 · Red Hat Integration · and others 1

fix ↗

Not affected

2 products (4 components) — because the vulnerable code is not present in the product

Red Hat OpenShift Container Platform 3.11 · Red Hat OpenShift Container Platform 4

XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.15, a Server-Side Forgery Request vulnerability can be activated when unmarshalling. The vulnerability may allow a remote attacker to request data from internal resources that are not publicly available 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 if 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.

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected products

x-stream · xstream

References