POODLE SSL / TLS Origin: Network OSI layer 6 · Presentation Last updated 18 Nov 2026

POODLE (CVE-2014-3566): SSLv3 is enabled on the server

A scanner flags SSLv3 as supported, which enables the POODLE downgrade attack.

Exact message you may see SSLv3 POODLE vulnerabilitySSL 3.0 Padding Oracle On Downgraded Legacy EncryptionSSLv3 enabledSSL Version 2 and 3 Protocol Detection
Seen on: SSL OpenSSL

Meaning

Disable SSLv3 entirely (nginx ssl_protocols TLSv1.2 TLSv1.3;, Apache SSLProtocol -all +TLSv1.2 +TLSv1.3, HAProxy ssl-min-ver TLSv1.2) and enable TLS_FALLBACK_SCSV. Check mail servers and appliances too.

Common causes

  • SSLv3 left enabled
  • Old defaults
  • Mail/FTP/LDAP TLS configs
  • Appliance management interface
  • Load balancer policy

⚡ Quick fix

  1. Disable SSLv3 on all listeners
  2. Restart services
  3. Verify: openssl s_client -ssl3 -connect host:443 should fail

Detailed fix by platform

Shell

  1. openssl s_client -ssl3 -connect example.com:443 # should fail

How to diagnose

  1. SSLv3 — Disabled?
  2. Other services — Checked?
  3. SCSV — Enabled?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

ACM region — CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia) (SSL / TLS)ACM regionALB listener — ALB HTTPS listener: CertificateNotFound / default certificate missing or SNI certificate list incomplete (SSL / TLS)ALB listenerDjango — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)DjangoHeartbleed — Heartbleed (CVE-2014-0160): OpenSSL heartbeat extension vulnerable (SSL / TLS)HeartbleedROBOT — ROBOT attack (CVE-2017-13099): vulnerable RSA key exchange implementation (SSL / TLS)ROBOTSCSV — tlsv1 alert inappropriate fallback (TLS_FALLBACK_SCSV downgrade protection) (SSL / TLS)SCSVTimeout during connect (likely firewall problem) — Let's Encrypt: Fetching http://example.com/.well-known/acme-challenge/token: Timeout during connect (likely firewall problem) (SSL / TLS)Timeout during connec…TLS 1.0/1.1 — Security scan finding: TLS 1.0 and TLS 1.1 are enabled (deprecated protocols, PCI DSS) (SSL / TLS)TLS 1.0/1.1POODLE

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.