Impact
The vulnerability allows a user with the policymaker role to crash a RabbitMQ node by exhausting the atom table. Repeated HTTP requests to the endpoint /api/global-parameters/:name with a unique :name value cause RabbitMQ to convert each name to an atom using an unsafe binary conversion function. As the atom table is finite, a large number of unique names fills the table, leading the JVM to fail and the broker to terminate. This results in a denial of service for all clients connected to the broker.
Affected Systems
RabbitMQ server versions 4.0.0 through 4.0.21, 4.1.0 through 4.1.13, 4.2.0 through 4.2.6, and 4.3.0 are affected. The issue is fixed in version 4.0.22 and in all later releases 4.1.14, 4.2.7, and 4.3.1.
Risk and Exploitability
The CVSS score of 5.9 indicates a moderate severity, and the EPSS score is not published, with no listing in the CISA KEV catalog. Exploitation requires an account with the policymaker tag and involves sending a high volume of HTTP requests to the API endpoint from an external network. The resulting crash creates a service outage that impacts all producers and consumers relying on the compromised RabbitMQ instance.
OpenCVE Enrichment