Technology: rabbitmq
ID | Title | Description | Category | Technology | Tags |
---|---|---|---|---|---|
CRE-2024-0007 Critical Impact: 9/10 Mitigation: 8/10 | RabbitMQ Mnesia overloaded | The underlying Erlang process, Mnesia, is overloaded (`** WARNING ** Mnesia is overloaded`). | Message Queue Problems | rabbitmq | Known ProblemRabbitMQPublic |
CRE-2024-0008 High Impact: 9/10 Mitigation: 6/10 | RabbitMQ memory alarm | A RabbitMQ node has entered the “memory alarm” state because the total memory used by the Erlang VM (plus allocated binaries, ETS tables, and processes) has exceeded the configured `vm_memory_high_watermark`. While the alarm is active the broker applies flow-control, blocking publishers and pausing most ingress activity to protect itself from running out of RAM. | Message Queue Problems | rabbitmq | Known ProblemRabbitMQPublic |
CRE-2024-0014 High Impact: 8/10 Mitigation: 5/10 | RabbitMQ busy distribution port performance issue | The Erlang VM has reported a **`busy_dist_port`** condition, meaning the send buffer of a distribution port (used for inter-node traffic inside a RabbitMQ cluster) is full. When this happens the scheduler suspends the process owning the port, stalling inter-node replication, management calls, and any RabbitMQ process that must use that port. Throughput drops and latency rises until the buffer drains or the node is restarted. | Message Queue Performance | rabbitmq | Known ProblemRabbitMQPublic |
CRE-2025-0063 Medium Impact: 6/10 Mitigation: 3/10 | RabbitMQ disk monitor fails to initialize | - RabbitMQ's disk monitor process cannot start or retrieve free‐space metrics, preventing it from detecting low‐disk conditions. | Message Queue Problems | rabbitmq | RabbitMQDisk MonitorMonitoringPlugin |