[Openstack] [OSSG][OSSN] OpenSSL Heartbleed vulnerability can lead to OpenStack compromise

Nathan Kinder nkinder at redhat.com
Thu Apr 10 07:22:12 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

OpenSSL Heartbleed vulnerability can lead to OpenStack compromise
- ---

### Summary ###
A vulnerability in OpenSSL can lead to leaking of confidential data
protected by SSL/TLS in an OpenStack deployment.

### Affected Services / Software ###
Grizzly, Havana, OpenSSL

### Discussion ###
A vulnerability in OpenSSL code-named Heartbleed was recently discovered
that allows remote attackers limited access to data in the memory of any
service using OpenSSL to provide encryption for network communications.
This can include key material used for SSL/TLS, which means that any
confidential data that has been sent over SSL/TLS may be compromised.
For full details, see the following website that describes this
vulnerability in detail:

    http://heartbleed.com/

While OpenStack software itself is not directly affected, any deployment
of OpenStack is very likely using OpenSSL to provide SSL/TLS
functionality.

### Recommended Actions ###
It is recommended that you immediately update OpenSSL software on the
systems you use to run OpenStack services.  In most cases, you will want
to upgrade to OpenSSL version 1.0.1g, though it is recommended that you
review the exact affected version details on the Heartbleed website
referenced above.

After upgrading your OpenSSL software, you will need to restart any
services that use the OpenSSL libraries.  You can get a list of all
processes that have the old version of OpenSSL loaded by running the
following command:

    lsof | grep ssl | grep DEL

Any processes shown by the above command will need to be restarted, or
you can choose to restart your entire system if desired.  In an
OpenStack deployment, OpenSSL is commonly used to enable SSL/TLS
protection for OpenStack API endpoints, SSL terminators, databases,
message brokers, and Libvirt remote access.  In addition to the native
OpenStack services, some commonly used software that may need to be
restarted includes:

  Apache HTTPD
  Libvirt
  MySQL
  Nginx
  PostgreSQL
  Pound
  Qpid
  RabbitMQ
  Stud

It is also recommended that you treat your existing SSL/TLS keys as
compromised and generate new keys.  This includes keys used to enable
SSL/TLS protection for OpenStack API endpoints, databases, message
brokers, and libvirt remote access.

In addition, any confidential data such as credentials that have been
sent over a SSL/TLS connection may have been compromised.  It is
recommended that cloud administrators change any passwords, tokens, or
other credentials that may have been communicated over SSL/TLS.

### Contacts / References ###
This OSSN : https://wiki.openstack.org/wiki/OSSN/OSSN-0012
OpenStack Security ML : openstack-security at lists.openstack.org
OpenStack Security Group : https://launchpad.net/~openstack-ossg
Heartbleed Website: http://heartbleed.com/
CVE: CVE-2014-0160
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTRkakAAoJEJa+6E7Ri+EVosQH+wdOZ4H40S11XAEA5o5XZtVH
N6DXwFn4dt3t8U3cxAX5bG+ZR3JyrVKFvuoOlkKplovRkxGiaeJHNTx7Kdi78YPu
DUVRQ+ult/BLFZwaiF1b6JLczu03fmN2MGfUyeBdlfpVR7QpAo7VZDmtt3j3y2YB
edH4khC3b3cciZKXW0couk21ENqszNO/ydwB8Nnyd9W7xjStJvZXNB2FS3p2Nt5W
bdwso6AIw8UZAbGBRnmhIlHein4mxXjFlmIBveevHIkM4/eYM3leE5HyNmsXWd7w
7t+UXBvZaadDvjPgdx5blubfXEDomN08OHPX3yjD3f3R8coZSMBcK+cCFYKeBDU=
=CQrS
-----END PGP SIGNATURE-----



More information about the Openstack mailing list