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 issue affects the amqp091-go library versions prior to 1.13.0.
What happened
An early warning has been issued for a critical security weakness in the AMQP client's TLS configuration generator. The amqp091-go library, used for AMQP communication in Go applications, is affected. The weakness lies in the library's initialization of the TLS configuration without explicitly defining the minimum TLS version. This could potentially allow negotiation of insecure TLS protocols, posing a significant security risk.
The affected versions of the amqp091-go library are those prior to 1.13.0. It is crucial for software engineers to assess whether their applications are using an affected version of this library. If so, they should consider upgrading to a version that explicitly sets the minimum TLS version in the TLS configuration to mitigate the risk.
What to do about it
- Identify if your application uses the amqp091-go library and check the version.
- If your application uses a version of amqp091-go prior to 1.13.0, upgrade to version 1.13.0 or later.
- Ensure that the upgraded version explicitly sets the minimum TLS version in the TLS configuration.
- Monitor the primary sources for updates on this vulnerability.
- Consider reviewing other dependencies for similar vulnerabilities.
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?
You are affected if your application uses the amqp091-go library and the version is prior to 1.13.0.
What should I do right now?
Check the version of amqp091-go your application uses. If it is prior to 1.13.0, upgrade to version 1.13.0 or later.
Is there an official fix available?
Yes, version 1.13.0 of the amqp091-go library is the patched version.
Should I be concerned about exploitation in the wild?
There is no confirmed report of this vulnerability being exploited in the wild at this time. However, it is still critical to address the vulnerability to prevent potential exploitation.
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