github.com/rabbitmq/amqp091-go
Affected
- introduced
0, fixed1.13.0(semver)
Fixed versions
1.13.0
Fix
- Fixed version
1.13.0go get github.com/rabbitmq/[email protected]
Advisory
Also known as: CVE-2026-77403, GO-2026-6503
RabbitMQ amqp091-go: Denial of Service via Sub-Spec Frame Size Negotiation
Summary
A Denial of Service (DoS) vulnerability exists in the AMQP client's connection negotiation logic. The AMQP specification explicitly mandates a strict minimum frame size of 4096 bytes to prevent pathological packet fragmentation. While the library defines a frameMinSize = 4096 constant, the connection negotiation loop fails to enforce this boundary, blindly accepting whatever maximum frame size (FrameMax) the server advertises during the handshake.
If a client connects to a malicious or compromised AMQP broker that advertises an extremely low FrameMax (such as 1 byte), the negotiation succeeds. Consequently, every subsequent message transmission is forced to splinter into thousands or millions of single-byte frames, causing massive CPU overhead, thread contention, and a near-instantaneous application freeze.
---
Vulnerability Details
Mechanism
During the connection establishment phase, the client and server negotiate connection parameters—including maximum channel count, heartbeat intervals, and maximum frame sizes. The vulnerability is located where the client accepts the server's tuning parameters:
// Connection negotiation logic maps server values directly without validation
if serverSettings.FrameMax > 0 {
// VULNERABILITY: Lacks a floor validation check against frameMinSize (4096)
c.config.FrameMax = serverSettings.FrameMax
}
Because there is no conditional check asserting that serverSettings.FrameMax >= frameMinSize, a value below the protocol specification floor is successfully registered. When the application later passes data payloads to the frame writer, the chunking algorithm splits the payload using the negotiated FrameMax value as its chunk window divisor.
Impact
When FrameMax is set to an absurdly low threshold (e.g., 1 to 10 bytes):
---
Attack Vector
An attacker who compromises an upstream AMQP broker, performs a Man-in-the-Middle (MitM) interception, or tricks an application into connecting to an unauthorized external rogue broker can trigger this vulnerability:
connection.tune phase, the rogue server returns a FrameMax value of 1.High Basis: The source's own band: HIGH
0, fixed 1.13.0 (semver)1.13.0
1.13.0go get github.com/rabbitmq/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0