CVE-2017-2637: Critical severity red hat openstack for ibm power vulnerability
A design flaw issue was found in the Red Hat OpenStack Platform director use of TripleO to enable libvirtd based live-migration. Libvirtd is deployed by default (by director) listening on 0.0.0.0 (all interfaces) with no-authentication or encryption. Anyone able to make a TCP connection to any compute host IP address, including 127.0.0.1, other loopback interface addresses, or in some cases possibly addresses that have been exposed beyond the management interface, could use this to open a virsh session to the libvirtd instance and gain control of virtual machine instances or possibly take over the host.
Other sources
OSP director was found to deploy libvirtd listening on 0.0.0.0 with no-authentication and in some cases no network ACL's. Anyone able to make a tcp connection to any compute host IP address, including 127.0.0.1, other loopback interface addresses or in some cases even those exposed beyond the management interface, could use this to open a virsh session to the libvirtd instance and gain control of virtual machine instances or possibly take over the host.
External References:
https://access.redhat.com/solutions/3022771 https://wiki.openstack.org/wiki/OSSN/OSSN-0007
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-2637?
The severity of CVE-2017-2637 is classified as critical due to the potential for unauthorized access to sensitive data.
How do I fix CVE-2017-2637?
To fix CVE-2017-2637, you should configure libvirtd to listen only on the localhost interface and implement authentication and encryption.
What versions of Red Hat OpenStack are affected by CVE-2017-2637?
CVE-2017-2637 affects Red Hat OpenStack versions 7.0, 8, 9, and 10.
What is the impact of CVE-2017-2637 exploitation?
Exploitation of CVE-2017-2637 could allow an attacker to gain unauthorized control over live migrations of virtual machines.
Is there a patch available for CVE-2017-2637?
Yes, a patch is available and can be applied through Red Hat's errata for the affected OpenStack versions.