Rabbitmq amqp091-go
amqp091-go has a Potential Memory Exhaustion/Protocol Violation via Broker-Controlled Oversized Payload
amqp091-go is a Go AMQP 0.9.1 client. Before version 1.13.0, a compromised or malicious AMQP broker can force the client to allocate resources for and process content body frames that exceed the negotiated frame_max limit. This can lead to unexpected memory consumption or application-layer denial of service (DoS), bypassing the protocol's built-in framing constraints. Version 1.13.0 contains a fix. No known workarounds are available.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.9high · scored by CNA · CWE-770
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
rabbitmq amqp091-go
- < 1.13.0
Fixed in 1.13.0
Mitigation
Upgrade amqp091-go to 1.13.0 or later.
References
- Vendor advisory github.com/rabbitmq/amqp091-go/security/adviso…
- Patch github.com/rabbitmq/amqp091-go/pull/353
- Patch github.com/rabbitmq/amqp091-go/commit/6beb7b51…
1 more
- Release notes github.com/rabbitmq/amqp091-go/releases/tag/v1…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.