AMQP Client URI Vulnerability in amqp091-go: Early Warning
- Severity
- HIGH
- Affected component
- rabbitmq (go)
- Patched version
- Not yet available
An early warning has been issued for a query parameter injection vulnerability in the AMQP client's connection URI formatting logic. This vulnerability affects the amqp091-go package.
What happened
An early warning has been issued for a query parameter injection vulnerability in the AMQP client's connection URI formatting logic. This vulnerability exists because TLS-related filesystem paths are appended directly to the URI's query string using string concatenation rather than secure URL encoding. This could allow an attacker to inject malicious parameters into the connection configuration.
The affected component is the amqp091-go package, specifically versions prior to 1.13.0. No authoritative version range for the rabbitmq (go) component has been published yet. It is recommended to upgrade to the latest version of amqp091-go and ensure that TLS file paths do not contain special characters that could be misinterpreted as parameter separators.
What to do about it
- Upgrade to the latest version of amqp091-go.
- Ensure that TLS file paths do not contain special characters that could be misinterpreted as parameter separators.
- Monitor the primary sources for updates on this vulnerability.
How 0Day would have caught this
rabbitmq 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 you are using the amqp091-go package in versions prior to 1.13.0. The impact on the rabbitmq (go) component is under investigation.
What should I do right now?
Upgrade to the latest version of amqp091-go and ensure that TLS file paths do not contain special characters that could be misinterpreted as parameter separators. Monitor the primary sources for updates on this vulnerability.
Has this been exploited in the wild?
No, this vulnerability has not been reported as exploited in the wild.
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