The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. maxBodyLebgth was not used when receiving Message objects. Attackers could send a very large Message causing a memory overflow and triggering an OOM Error. Users of RabbitMQ may suffer from DoS attacks from RabbitMQ Java client which will ultimately exhaust the memory of the consumer. This vulnerability was patched in version 5.18.0.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Rabbitmq_java_client | Vmware | * | 5.18.0 (excluding) |
| Rabbitmq-java-client | Ubuntu | bionic | * |
| Rabbitmq-java-client | Ubuntu | focal | * |
| Rabbitmq-java-client | Ubuntu | lunar | * |
| Rabbitmq-java-client | Ubuntu | mantic | * |
| Rabbitmq-java-client | Ubuntu | oracular | * |
| Rabbitmq-java-client | Ubuntu | trusty | * |
| Rabbitmq-java-client | Ubuntu | upstream | * |
| Rabbitmq-java-client | 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.