Описание
An issue was discovered in OpenStack oslo.messaging 1.0.0 through 17.3.0. The oslo.messaging RabbitMQ driver does not perform TLS hostname verification when connecting to the message broker. When ssl_ca_file is configured, the driver enables certificate chain validation but does not pass the expected broker hostname into the underlying TLS stack. Any certificate signed by the deployment CA is accepted regardless of hostname, allowing an attacker who can intercept control-plane traffic to impersonate the RabbitMQ broker and perform a man-in-the-middle attack on RPC and notification traffic. All OpenStack services using oslo.messaging with RabbitMQ over TLS are affected.
A flaw was found in OpenStack oslo.messaging. The RabbitMQ driver does not properly verify the hostname of the message broker when establishing a TLS (Transport Layer Security) connection. An attacker capable of intercepting control-plane network traffic can exploit this vulnerability to impersonate the RabbitMQ broker. This allows the attacker to perform a man-in-the-middle attack, potentially leading to the disclosure or manipulation of sensitive RPC (Remote Procedure Call) and notification traffic.
Отчет
This Important flaw in OpenStack oslo.messaging impacts Red Hat OpenStack Platform and OpenShift Container Platform when using RabbitMQ with TLS. The vulnerability arises from the RabbitMQ driver's failure to perform proper hostname verification during TLS connection establishment. This oversight enables an attacker capable of intercepting control-plane network traffic to impersonate the RabbitMQ broker, potentially leading to man-in-the-middle attacks that compromise the confidentiality and integrity of sensitive RPC and notification data.
Меры по смягчению последствий
To mitigate the risk of man-in-the-middle attacks, restrict network access to the RabbitMQ message broker. Configure firewall rules to permit inbound connections to the RabbitMQ port (typically 5672 or 5671 for AMQPS) only from authorized hosts and services within the control plane. This operational measure reduces the exposure to attackers attempting to intercept and impersonate the broker.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat OpenShift Container Platform 4 | python-oslo-messaging | Affected | ||
| Red Hat OpenStack Platform 16.2 | python-oslo-messaging | Affected | ||
| Red Hat OpenStack Platform 17.1 | python-oslo-messaging | Affected | ||
| Red Hat OpenStack Platform 18.0 | python-oslo-messaging | Affected |
Показывать по
Дополнительная информация
Статус:
EPSS
7.4 High
CVSS3
Связанные уязвимости
An issue was discovered in OpenStack oslo.messaging 1.0.0 through 17.3.0. The oslo.messaging RabbitMQ driver does not perform TLS hostname verification when connecting to the message broker. When ssl_ca_file is configured, the driver enables certificate chain validation but does not pass the expected broker hostname into the underlying TLS stack. Any certificate signed by the deployment CA is accepted regardless of hostname, allowing an attacker who can intercept control-plane traffic to impersonate the RabbitMQ broker and perform a man-in-the-middle attack on RPC and notification traffic. All OpenStack services using oslo.messaging with RabbitMQ over TLS are affected.
An issue was discovered in OpenStack oslo.messaging 1.0.0 through 17.3.0. The oslo.messaging RabbitMQ driver does not perform TLS hostname verification when connecting to the message broker. When ssl_ca_file is configured, the driver enables certificate chain validation but does not pass the expected broker hostname into the underlying TLS stack. Any certificate signed by the deployment CA is accepted regardless of hostname, allowing an attacker who can intercept control-plane traffic to impersonate the RabbitMQ broker and perform a man-in-the-middle attack on RPC and notification traffic. All OpenStack services using oslo.messaging with RabbitMQ over TLS are affected.
An issue was discovered in OpenStack oslo.messaging 1.0.0 through 17.3 ...
OpenStack oslo.messaging does not verify RabbitMQ broker hostname during TLS handshake
EPSS
7.4 High
CVSS3