Researchers identified that the library fails to enforce this established constraint when receiving content body frames. If a malicious or compromised broker transmits a frame header declaring a payload size that exceeds the agreed-upon frame_max, the library trustfully accepts the value. This results in the client performing memory allocations dictated by the broker rather than the negotiated protocol limits. An attacker acting as a rogue broker can exploit this behavior by sending frames with excessively large declared sizes, leading to significant memory exhaustion and potential Out-Of-Memory (OOM) application crashes. This vulnerability represents a failure of the client to adhere to the security constraints defined by the AMQP 0-9-1 specification.

Impact

Successful exploitation leads to an application-layer Denial of Service (DoS) against any service or client utilizing the amqp091-go library to connect to an untrusted or compromised AMQP broker. This can result in service instability, application crashes, and potential disruption of dependent message-processing workflows.

Recommendation

• Upgrade the amqp091-go library to version 1.13.0 or later immediately to incorporate proper frame size validation.
• Review connection configurations to ensure that clients are only interacting with trusted or hardened AMQP broker infrastructure.
• Monitor application memory metrics and infrastructure logs for anomalous growth or OOM events associated with the Go service binary.