CVE-2014-3566 - SSLv3 Poodle - Final Resolution

Skip to first unread message

Greg Oehmen

Oct 27, 2014, 1:17:30 PM10/27/14
to vcap-dev, bosh-users,

CVE-2014-3566  -   SSLv3 Poodle


October 27, 2014




The SSL protocol 3.0, as used in OpenSSL through 1.0.1i

Versions Affected:



SSL 3.0 [RFC6101] is an obsolete and insecure protocol. While for most practical

purposes it has been replaced by its successors TLS 1.0 [RFC2246], TLS 1.1 [RFC4346],

and TLS 1.2 [RFC5246], many TLS implementations remain backwards ­compatible with

SSL 3.0 to interoperate with legacy systems in the interest of a smooth user experience.

The protocol handshake provides for authenticated version negotiation, so normally the

latest protocol version common to the client and the server will be used.  However, even if a client and server both support a version of TLS, the security level offered by SSL 3.0 is still relevant since many clients implement a protocol downgrade dance to work around server­side interoperability bugs. Attackers can exploit the downgrade dance and break the cryptographic security of SSL 3.0. Our POODLE attack (Padding Oracle On Downgraded Legacy Encryption) will allow them, for example, to steal “secure” HTTP cookies (or other bearer tokens such as HTTP Authorization header contents).

Affected Pivotal Products and Versions:

Severity is Moderate unless otherwise noted.

  • BOSH: All versions of Cloud Foundry BOSH stemcells prior to 2748 have SSLv3 enabled and thus are vulnerable to CVE-2014-3356

  • Elastic Runtime: CF Release 190 and below


The Cloud Foundry team is actively working on patch releases to BOSH and Elastic Runtime that resolve all vulnerabilities for CVE-2014-3566.  The Cloud Foundry project recommends that HAProxy or any other ELBs is use be updated to disable SSLv3 as a workaround that resolves CVE-2014-3566.  

  • The CF team released CF v.191 that ships with SSLv3 disabled.

  • The CF team has published new BOSH stemcells v.2748 that resolve all vulnerabilities for CVE-2014-3566.  

  • CF users who are not using CF’s HAProxy for load balancing and instead have added their own load balancing solution are strongly advised to disable SSLv3 in the given load balancer.


Google researchers Bodo Möller, Thai Duong, and Krzysztof Kotowicz released a paper discussing a serious bug in SSL 3.0 that allows attackers to conduct man-in-the-middle attacks and decrypt the traffic between Web servers and end users.



* Pivotal Security Team page

* [This advisory]



BOSH Stemcells

Cloud Foundry Release

Reply all
Reply to author
0 new messages