RabbitMQ amqp091-go
RabbitMQ amqp091-go: Resource Exhaustion (OOM) via Unbounded Body Buffer Allocation
RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 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/346
- Patch github.com/rabbitmq/amqp091-go/commit/91b65fa0…
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.