| Package | Affected versions | Patched versions |
|---|---|---|
| com.thoughtworks.xstream:xstream | < 1.4.16 | 1.4.16 |
| activemq | = 5.16.0= 5.16.1< 5.15.14 | 5.15.14 |
| jmeter | < 5.5 | 5.5 |
| banking enterprise default management | = 2.10.0= 2.12.0 | |
| banking platform | = 2.12.0= 2.4.0= 2.7.1= 2.9.0 | |
| banking virtual account management | = 14.2.0= 14.3.0= 14.5.0 | |
| business activity monitoring |
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 a server-side forgery request. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.
If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16
See workarounds for the different versions covering all CVEs.
See full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for CVE-2021-21342.
钟潦贵 (Liaogui Zhong) found and reported the issue to XStream and provided the required information to reproduce it.
If you have any questions or comments about this advisory:
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free= 11.1.1.9.0= 12.2.1.3.0= 12.2.1.4.0| communications brm - elastic charging engine | = 12.0.0.3 |
| communications policy management | = 12.5.0 |
| communications unified inventory management | = 7.3.2= 7.3.4= 7.3.5= 7.4.0= 7.4.1 |
| retail xstore point of service | = 16.0.6= 17.0.4= 18.0.3= 19.0.2 |
| webcenter portal | = 11.1.1.9.0= 12.2.1.3.0= 12.2.1.4.0 |
| xstream | < 1.4.16 | 1.4.16 |