amqp091-go: Pre-negotiation frame limit is not enforced to 4KB
rabbitmq amqp091-go
rabbitmq amqp091-go
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rabbitmq/amqp091-go Go |
|
|
amqp091-go is a Go AMQP 0.9.1 client. From 1.13.0 until 1.14.0, the frame-size mitigation from the prior allocation advisory can be bypassed before connection.tune completes because Connection.maxFrameSize uses zero for both the not-yet-negotiated and negotiated-unlimited states. A malicious or compromised AMQP peer can send a short body-frame header with a large declared payload length, causing ReadFrame and the body-frame parser to allocate attacker-selected memory before the payload is received or the frame's protocol state is rejected. The condition is reachable through public Open even when Config.FrameSize is set to the protocol minimum and can cause severe memory pressure, out-of-memory termination, or loss of the client process before authentication completes. This issue is fixed in version 1.14.0.
From the CVE record · GitHub_M
Before connection tuning completes, amqp091-go can allocate memory based on a body-frame payload length declared by an AMQP peer, bypassing its frame-size mitigation. A malicious or compromised peer can cause severe memory pressure or terminate the client process before authentication completes, even when Config.FrameSize is set to the protocol minimum.
Engineers running applications that use github.com/rabbitmq/amqp091-go versions earlier than 1.14.0 should check their dependencies.