VMware is aware of this issue. See the workaround section below for additional information.
Workaround:
Prerequisites
- Please take simultaneous non-memory snapshots of each virtual appliance(s) in the cluster.
Procedure
- To prevent future scans from reporting this vulnerability, you may add the following flag in the ssl_options section of the /etc/rabbitmq/rabbitmq.config file:
{client_renegotiation, false}
For example: Add this between {verify, verify_peer} and {fail_if_no_peer_cert,false} as shown below:
{verify, verify_peer},
{client_renegotiation, false},
{fail_if_no_peer_cert, false}
- Restart the RabbitMQ server service:
service rabbitmq-server restart
Note: This should be done on both appliances during a maintenance window as restarting rabbitmq-server can cause unexpected product behavior such as failing requests in flight.