CVE-2014-3566 SSLV3 POODLE




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

Versions Affected
  • SSLv3

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 2743 and prior use SSLv3 and thus are vulnerable to CVE-2014-3356
  • Elastic Runtime: to
  • PCF Ops Manager: to
  • PCF Ops Metrics: to
  • tc Server 2.9.0 to 2.9.7 and 3.0.0 to 3.0.1. Previous, unsupported tc Server versions may also be affected.

The Pivotal CF team is actively working on patch releases to Elastic Runtime, Operations Manager and Ops Metrics 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 Pivotal CF team is creating a new CF release that will ship with SSLv3 disabled. Currently targeting v191 as that release.
  • The Pivotal CF team is actively working on new BOSH stemcells that resolve all vulnerabilities for CVE-2014-3566.
  • PCF customers 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.
  • PCF Ops Manager: Team is patching nginx to disable SSLv3
  • PCF Ops Metrics: Team is cutting 1.3.3 which will ship with a disabled SSLv3

The details published by the Apache Software Foundation for mitigating this attack for Apache Tomcat apply equally to tc Runtime instances. The tc Server team is tracking the work of the Apache Tomcat project to release versions of Apache Tomcat that disable SSLv3 by default. tc Server releases will follow the releases from the Apache Software Foundation.


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.


2014-Oct-16: Initial vulnerability report published.

2013-Nov-03: Updated to include tc Server information