RabbitMQ amqp091-go: Missing Explicit TLS Minimum Version Configuration In URI Parser
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| rabbitmq | amqp091-go | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Rabbitmq | Amqp091-go |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-33mj-cw25-m34h | RabbitMQ amqp091-go: Missing Explicit TLS Minimum Version Configuration In URI Parser |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.282% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Rabbitmq
Rabbitmq amqp091-go |
|
| Vendors & Products |
Rabbitmq
Rabbitmq amqp091-go |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, tlsConfigFromURI in uri.go creates tls.Config values without setting MinVersion to tls.VersionTLS12. Builds using a Go runtime whose default permits TLS 1.0 or TLS 1.1 can therefore negotiate an obsolete protocol version when connecting through an amqps URI. A network attacker able to influence TLS negotiation with such a legacy build may weaken transport protection for AMQP messages and credentials. This issue is fixed in version 1.13.0. | |
| Title | RabbitMQ amqp091-go: Missing Explicit TLS Minimum Version Configuration In URI Parser | |
| Weaknesses | CWE-326 | |
| References |
| |
| Metrics |
cvssV4_0
|