RabbitMQ rabbitmq-server
RabbitMQ: Stream-protocol frame length never validated against frame_max
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the stream protocol stored the FrameMax value negotiated during the Tune handshake but did not compare it with an inbound frame's declared length before buffering the frame. With the stream plugin enabled, a remote client could therefore cause excessive memory pressure and denial of service by declaring an oversized frame. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by NVD · CWE-770
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
rabbitmq rabbitmq-server
- >= 3.13.0, < 3.13.15
- >= 4.0.0, < 4.0.20
- >= 4.1.0, < 4.1.11
- >= 4.2.0, < 4.2.6
Fixed in 3.13.15, 4.0.20, 4.1.11, 4.2.6
Mitigation
Upgrade rabbitmq-server to 3.13.15 or 4.0.20 or 4.1.11 or 4.2.6 or later.
References
- Vendor advisory github.com/rabbitmq/rabbitmq-server/security/a…
- Release notes github.com/rabbitmq/rabbitmq-server/releases/t…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.