The Java OpenWire protocol marshaller is vulnerable to Remote Code Execution. This vulnerability may allow a remote attacker with network access to either a Java-based OpenWire broker or client to run arbitrary shell commands by manipulating serialized class types in the OpenWire protocol to cause either the client or the broker (respectively) to instantiate any class on the classpath.
Users are recommended to upgrade both brokers and clients to version 5.15.16, 5.16.7, 5.17.6, or 5.18.3 which fixes this issue.
The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Activemq | Apache | * | 5.15.16 (excluding) |
| Activemq | Apache | 5.16.0 (including) | 5.16.7 (excluding) |
| Activemq | Apache | 5.17.0 (including) | 5.17.6 (excluding) |
| Activemq | Apache | 5.18.0 (including) | 5.18.3 (excluding) |
| AMQ 6.3 openshift container image | RedHat | * | |
| AMQ Broker 7.10.5 | RedHat | activemq-openwire | * |
| AMQ Broker 7.11.4 | RedHat | activemq-openwire | * |
| Red Hat Fuse 7.12.1 | RedHat | activemq-openwire | * |
| Red Hat Fuse/AMQ 6.3.20 | RedHat | activemq-openwire | * |
| RHEL-7 based Middleware Containers | RedHat | jboss-amq-6/amq63-openshift:1.4-50 | * |
| Activemq | Ubuntu | bionic | * |
| Activemq | Ubuntu | esm-apps/bionic | * |
| Activemq | Ubuntu | esm-apps/focal | * |
| Activemq | Ubuntu | esm-apps/jammy | * |
| Activemq | Ubuntu | esm-apps/xenial | * |
| Activemq | Ubuntu | focal | * |
| Activemq | Ubuntu | jammy | * |
| Activemq | Ubuntu | lunar | * |
| Activemq | Ubuntu | mantic | * |
| Activemq | Ubuntu | trusty | * |
| Activemq | Ubuntu | upstream | * |
| Activemq | Ubuntu | xenial | * |
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.