Poodle Attack on Cloudflare

The Poodle attack (Padding Oracle On Downgraded Legacy Encryption) exploits fallback behavior in TLS implementations that support SSLv3. In Cloudflare, this typically arises when a backend or origin configuration still permits SSLv3 ciphers or when legacy clients negotiate SSLv3 during the handshake. Cloudflare’s edge proxies may terminate TLS and forward requests to origin servers that accept SSLv3, creating a mixed-mode scenario where an attacker can perform chosen-ciphertext decryption via the CBC padding oracle. Specific Cloudflare configuration patterns include allowing legacy cipher suites in custom SSL profiles or when integrating with older load balancers that do not disable SSLv3. The attack manifests as repeated padding error responses that leak plaintext bytes one byte at a time, often targeting session cookies or authentication tokens.

Within Cloudflare’s request processing pipeline, Poodle-relevant code paths involve the SSL/TLS termination module and the cipher suite negotiation logic. If an origin server behind Cloudflare accepts SSLv3, an attacker can force or observe fallback attempts, using the padding validation responses to infer data. For example, a misconfigured custom page rule or a legacy origin with weak cipher configuration might expose CBC-mode ciphers without proper anti-downgrade protections. This is especially risky when Cloudflare is in flexible or full mode and the origin does not enforce modern TLS, allowing the attacker to strip or downgrade security parameters to SSLv3.

Concrete attack patterns include sending modified TLS records that trigger SSLv3 fallback and measuring timing or error differences to detect padding validity. In Cloudflare environments, this can occur when traffic originates from constrained devices that support SSLv3 or when testing tools deliberately request SSLv3. Because Cloudflare supports a wide range of cipher suites for compatibility, operators must explicitly disable SSLv3 and prefer modern suites to avoid these oracle conditions.

Detecting Poodle risks in Cloudflare involves verifying that SSLv3 is disabled across all configurations, including custom SSL profiles, page rules, and origin settings. Use middleBrick to scan your Cloudflare-facing endpoints and review the findings related to encryption and protocol support. The scanner checks for the presence of SSLv3 in the negotiated cipher suites and flags configurations that allow legacy fallback. For example, after submitting your Cloudflare domain to middleBrick, you will receive a security score with an Encryption category breakdown that highlights whether SSLv3 or weak CBC-based ciphers are enabled.

In the middleBrick output, look for findings under the Encryption and Data Exposure categories that mention SSLv3, CBC mode, or missing anti-downgrade protections. The tool cross-references your runtime behavior with the provided OpenAPI/Swagger specification (if available) and runtime responses to identify mismatches between declared and actual security posture. If SSLv3 is detected or if the scan identifies excessive CBC usage without modern mitigations, prioritize remediation. Continuous monitoring in the Pro plan can alert you if a configuration change reintroduces SSLv3 support, helping maintain a strong encryption posture without manual audits.

Remediation focuses on disabling SSLv3 and enforcing strong cipher suites within Cloudflare configurations. In the Cloudflare dashboard, ensure that SSL mode is set to "Full" or "Full (Strict)" and that legacy ciphers are not enabled. When using custom SSL profiles or API integrations, explicitly configure cipher lists to exclude SSLv3 and prefer TLS 1.2 and TLS 1.3 suites. For environments that require origin-side controls, apply similar settings on backend servers and libraries.

Example configuration using Cloudflare API to disable weak protocols and enforce modern ciphers (replace <ZONE_ID> with your zone identifier):

curl -X PATCH "https://api.cloudflare.com/client/v4/zones/<ZONE_ID>/settings/ssl" \
  -H "Authorization: Bearer <API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "value": "modern"
  }'

This sets the SSL profile to modern, which disables SSLv3 and deprecated ciphers. For granular control, specify a custom cipher suite list that excludes CBC where possible and prioritizes AEAD ciphers. In origin configurations, ensure that servers do not accept SSLv3 by disabling it in the TLS library (for example, in OpenSSL):

SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv3);

Combine this with strong cipher suite ordering and session resumption policies that do not rely on insecure fallback. Regular scans with middleBrick validate that the changes are effective and that no new Poodle-relevant vectors appear after updates to routing rules or origin certificates.