REDHAT-BUG-2484835: High severity Openstack oslo.messaging vulnerability
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 sslcafile 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2484835?
The severity of REDHAT-BUG-2484835 is classified as high with a score of 7.
What issue does REDHAT-BUG-2484835 describe?
REDHAT-BUG-2484835 describes a vulnerability in OpenStack oslo.messaging where the RabbitMQ driver fails to perform TLS hostname verification.
Which versions of OpenStack oslo.messaging are affected by REDHAT-BUG-2484835?
OpenStack oslo.messaging versions 1.0.0 through 17.3.0 are affected by REDHAT-BUG-2484835.
How do I fix REDHAT-BUG-2484835?
To fix REDHAT-BUG-2484835, ensure that the RabbitMQ driver is properly configured to perform TLS hostname verification.
What component of OpenStack is vulnerable in REDHAT-BUG-2484835?
The vulnerable component in REDHAT-BUG-2484835 is the RabbitMQ driver of OpenStack oslo.messaging.