Cybersecurity glossary
What is POODLE (CVE-2014-3566)?
Learn what the POODLE attack (CVE-2014-3566) is, how SSL 3.0 CBC padding oracles enabled decryption, why TLS fallback mattered, and how disabling SSL 3.0 eliminates the classic risk.
Definition
POODLE (Padding Oracle On Downgraded Legacy Encryption), tracked as CVE-2014-3566, is an attack against SSL 3.0 CBC-mode cipher suites that exploits padding validation weaknesses—often after forcing a protocol downgrade—to decrypt HTTP cookies and other secrets byte by byte.
Why POODLE mattered
In 2014, researchers showed that SSL 3.0—already ancient—still lurked as a fallback for compatibility. POODLE (Padding Oracle On Downgraded Legacy Encryption), tracked as CVE-2014-3566, demonstrated that SSL 3.0 CBC padding could be abused as an oracle to decrypt secrets.
The practical path was often a man-in-the-middle that forced a downgrade from TLS to SSL 3.0, then decrypted cookies one byte at a time. The industry response was decisive: turn SSL 3.0 off.
How POODLE works
Obtain a MITM position
The attacker can modify handshake messages between browser and server.
Force SSL 3.0 fallback
Protocol negotiation is manipulated so both sides agree on SSL 3.0 CBC.
Align a secret byte
Attacker-controlled plaintext placement helps isolate cookie bytes in CBC blocks.
Use padding oracle behavior
Differences in how invalid padding is handled reveal information about guessed bytes.
Recover secrets iteratively
Repeated requests reconstruct cookies or other HTTP secrets.
Disable SSL 3.0
Operators and browsers remove the vulnerable protocol entirely.
POODLE among TLS failures
| Property | POODLE | BEAST | Heartbleed |
|---|---|---|---|
| CVE | CVE-2014-3566 | CVE-2011-3389 | CVE-2014-0160 |
| Root issue | SSL 3.0 CBC padding oracle / downgrade | TLS 1.0 CBC IV predictability | OpenSSL memory disclosure |
| Primary fix | Disable SSL 3.0; modern TLS only | Upgrade TLS; avoid vulnerable CBC paths | Patch OpenSSL; rotate secrets |
Mitigation checklist
- Disable SSL 3.0 (and SSL 2.0) on all TLS terminators and clients.
- Require TLS 1.2+ for public services; plan removal of TLS 1.0/1.1.
- Patch libraries for any TLS CBC padding oracle implementation bugs.
- Verify CDNs and load balancers do not re-enable SSL 3.0 for legacy clients.
- Scan for SSL 3.0 acceptance after configuration changes.
- Prefer modern AEAD cipher suites in TLS 1.2/1.3 configurations.
- Document that 'maximum compatibility' must not resurrect SSL 3.0.
- Treat remaining SSL 3.0 endpoints as critical findings.
The practical takeaway
POODLE (CVE-2014-3566) showed that SSL 3.0 CBC encryption could leak secrets—especially after forced downgrades. The durable fix is to refuse SSL 3.0 entirely and run modern TLS.
If any edge still accepts SSL 3.0 “for one old scanner,” it recreates a closed chapter of web crypto history. Disable it.
Related security terms
BEAST (CVE-2011-3389)
An earlier CBC-related TLS attack that also pushed the ecosystem off obsolete constructions.
SSL/TLS
The protocol family whose SSL 3.0 version POODLE targeted.
HTTPS
The common deployment of SSL/TLS where POODLE threatened cookie confidentiality.
Man-in-the-Middle (MITM)
Network position used to force downgrades and observe ciphertext.
Frequently asked questions
What is POODLE in simple terms?
POODLE is an attack that can decrypt secrets from old SSL 3.0 encrypted web traffic by abusing how padding was checked. Attackers often force a browser and server to fall back to SSL 3.0 first.
What is CVE-2014-3566?
CVE-2014-3566 identifies the classic POODLE vulnerability in SSL 3.0 CBC cipher suites.
Does POODLE affect modern TLS 1.2/1.3 only sites?
If SSL 3.0 is completely disabled on clients and servers, classic POODLE does not apply. Residual risk remains on legacy systems that still allow SSL 3.0 negotiation.
What was TLS_FALLBACK_SCSV?
A signaling cipher suite value designed to help prevent protocol downgrade attacks used in POODLE-style scenarios, complementary to simply disabling SSL 3.0.
Was there a TLS POODLE variant?
Researchers also discussed padding oracle issues in some TLS implementations’ CBC handling. The headline CVE-2014-3566 centers on SSL 3.0, while implementation bugs needed patches beyond protocol disablement.
How do you mitigate POODLE?
Disable SSL 3.0 everywhere, prefer TLS 1.2+, patch TLS libraries, and avoid CBC-focused legacy configurations.
What secrets were at risk?
Primarily HTTPS cookies and other HTTP secrets that could be aligned and decrypted through repeated padding-oracle observations.
References
Explore authoritative guidance and frameworks related to poodle (cve-2014-3566).
Explore every security definition
Return to the glossary to search by term, alias, starting letter, or security category.