XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is vulnerability which may allow a remote attacker to allocate 100% CPU time on the target system depending on CPU type or parallel execution of such a payload resulting in a denial of service only by manipulating the processed input stream. 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.
The product does not properly control the allocation and maintenance of a limited resource.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Oncommand_insight | Netapp | - (including) | - (including) |
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 2 | 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/bionic | * |
Libxstream-java | Ubuntu | esm-apps/focal | * |
Libxstream-java | Ubuntu | esm-apps/jammy | * |
Libxstream-java | Ubuntu | esm-apps/noble | * |
Libxstream-java | Ubuntu | esm-apps/xenial | * |
Libxstream-java | Ubuntu | esm-infra-legacy/trusty | * |
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 | * |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.