AMQP Client TLS Configuration Weakness: What Software Engineers Need to Know
- Severity
- HIGH
- Affected component
- amqp091-go (go)
- Affected versions
- < 1.13.0
- Patched version
- Not yet available
An early warning has been issued regarding a structural security weakness in the AMQP client's TLS configuration generator. This weakness could allow for the negotiation of obsolete and insecure TLS protocols, potentially exposing AMQP protocol data streams to well-known cryptographic vulnerabilities.
What happened
The reported weakness lies in the TLS configuration generator of the AMQP client, specifically within the amqp091-go package. This generator appears to lack an explicit configuration for the minimum TLS version, which could result in the negotiation of insecure TLS protocols. This situation could expose the AMQP protocol data stream to vulnerabilities associated with outdated cryptographic standards.
The affected component is the amqp091-go package for Go, with versions less than 1.13.0 reportedly vulnerable. The rabbitmq package for Go is also mentioned, but an authoritative version range has not been published. It is crucial for software engineers to assess their systems for the use of these components and versions to determine potential exposure.
What to do about it
- Upgrade to the latest version of amqp091-go to mitigate the risk of negotiating insecure TLS protocols.
- Ensure that the Go compiler toolchain is at least version 1.18.
- Monitor the primary sources for updates on the vulnerability and any official fixes that may be published.
- Consult the primary sources for the most current information on affected versions and patches.
How 0Day would have caught this
amqp091-go is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.
Frequently asked questions
Am I affected?
If your system uses the amqp091-go package for Go with a version less than 1.13.0, you may be affected. The impact on the rabbitmq package for Go is under investigation, and no authoritative version range has been published yet.
What should I do right now?
Immediately upgrade to the latest version of amqp091-go and ensure your Go compiler toolchain is at least version 1.18. Monitor the primary sources for updates on the vulnerability and any official fixes.
Is there an official fix available?
For amqp091-go, version 1.13.0 is reported to be a patched version. No official fix has been published for the rabbitmq package for Go yet. Continue to monitor the primary sources for updates.
Sources
- [GHSA-33mj-cw25-m34h] RabbitMQ amqp091-go: Missing Explicit TLS Minimum Version Configuration In URI Parser
- [GHSA-c5pq-fr2g-9jpf] RabbitMQ amqp091-go: Protocol Desynchronization and Frame Injection via Integer Overflow in readLongstr
- [GHSA-j497-x9hr-x34x] RabbitMQ amqp091-go: Silent Data Truncation and State Corruption via Shortstr Integer Overflow
- [GHSA-27gv-rfvv-22mv] RabbitMQ amqp091-go: Plaintext Credential Exposure via Exported PLAIN Authentication Struct Fields
- [GHSA-33mj-cw25-m34h] RabbitMQ amqp091-go: Missing Explicit TLS Minimum Version Configuration In URI Parser
- [GHSA-465g-fh3v-9jw4] RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection
- [GHSA-4v58-74mf-rjx3] RabbitMQ amqp091-go: Denial of Service via Malicious Field Length in AMQP Client