RabbitMQ: Stream listener does not enforce configured frame-size limit during authentication, permitting unauth'd mem-exhaust DoS
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.5%
exploitation probability
0.5%top 57% of all CVEs
observed exploitation
nono source reports it
RabbitMQ is a messaging and streaming broker. Prior to 4.2.6, the RabbitMQ stream listener does not enforce the configured stream frame-size limit while assembling frames during authentication and before Tune negotiation, allowing an unauthenticated remote client to declare oversized frame lengths and consume broker memory in rabbit_stream_core. This issue is fixed in version 4.2.6.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
rabbitmq · rabbitmq-serverReferences
https://github.com/rabbitmq/rabbitmq-server/commit/595ec28fa1621b1f2c28124e4e0466a8ad963547https://github.com/rabbitmq/rabbitmq-server/commit/773a49c4921e8be990262a2d609c35916825679ehttps://github.com/rabbitmq/rabbitmq-server/pull/16171https://github.com/rabbitmq/rabbitmq-server/pull/16173https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f364-87q5-j35q