CVE Vulnerabilities

CVE-2021-21343

Deserialization of Untrusted Data

Published: Mar 23, 2021 | Modified: Nov 07, 2023
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N
RedHat/V2
RedHat/V3
5.9 MODERATE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Ubuntu
MEDIUM

XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in the deletion of a file on the local host. No user is affected, who followed the recommendation to setup XStreams security framework with a whitelist limited to the minimal required types. If you rely on XStreams default blacklist of the Security Framework, you will have to use at least version 1.4.16.

Weakness

The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.

Affected Software

Name Vendor Start Version End Version
Xstream Xstream_project * 1.4.16 (excluding)
Red Hat Data Grid 8.2.0 RedHat xstream *
Red Hat Fuse 7.10 RedHat xstream *
Red Hat Integration RedHat xstream *
Red Hat Integration Camel Quarkus RedHat xstream *
RHDM 7.11.0 RedHat xstream *
RHPAM 7.11.0 RedHat xstream *
Libxstream-java Ubuntu bionic *
Libxstream-java Ubuntu devel *
Libxstream-java Ubuntu esm-apps/xenial *
Libxstream-java Ubuntu focal *
Libxstream-java Ubuntu groovy *
Libxstream-java Ubuntu hirsute *
Libxstream-java Ubuntu impish *
Libxstream-java Ubuntu jammy *
Libxstream-java Ubuntu kinetic *
Libxstream-java Ubuntu lunar *
Libxstream-java Ubuntu mantic *
Libxstream-java Ubuntu noble *
Libxstream-java Ubuntu oracular *
Libxstream-java Ubuntu trusty *
Libxstream-java Ubuntu trusty/esm *
Libxstream-java Ubuntu upstream *
Libxstream-java Ubuntu xenial *

Extended Description

It is often convenient to serialize objects for communication or to save them for later use. However, deserialized data or code can often be modified without using the provided accessor functions if it does not use cryptography to protect itself. Furthermore, any cryptography would still be client-side security – which is a dangerous security assumption. Data that is untrusted can not be trusted to be well-formed. When developers place no restrictions on “gadget chains,” or series of instances and method invocations that can self-execute during the deserialization process (i.e., before the object is returned to the caller), it is sometimes possible for attackers to leverage them to perform unauthorized actions, like generating a shell.

Potential Mitigations

  • Make fields transient to protect them from deserialization.
  • An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.

References