Heartbleed (CVE-2014-0160): OpenSSL heartbeat extension vulnerable
A scanner reports the server leaks memory through the TLS heartbeat bug.
Heartbleed vulnerabilityOpenSSL Heartbeat Information Disclosuressl-heartbleed VULNERABLEThe TLS heartbeat extension is vulnerable Meaning
This affects OpenSSL 1.0.1–1.0.1f. Upgrade OpenSSL (to a supported version), restart all services using it, revoke and reissue certificates and rotate keys/passwords as the memory may have leaked secrets. Modern systems should never show this; check old appliances and embedded devices.
Common causes
- OpenSSL 1.0.1 to 1.0.1f in use
- Old embedded device/appliance
- Statically linked OpenSSL in an app
- Service not restarted after patching
- Forgotten legacy server
⚡ Quick fix
- Upgrade OpenSSL and restart services
- Reissue certificates and rotate secrets
- Replace or isolate the legacy device
Detailed fix by platform
Shell
- bash
openssl version -a nmap -p 443 --script ssl-heartbleed example.com
How to diagnose
- OpenSSL — 1.0.1a-f?
- Services — Restarted?
- Keys — Rotated?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- bad decrypt openssl: bad decrypt / Could not read private key — wrong passphrase or cipher
- ca md too weak / ee key too small OpenSSL: error:0A00018E:SSL routines::ca md too weak / error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small
- Django Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port)
Most viewed in SSL / TLS
- HTTPSConnectionPool: Max retries exceeded (SSLError) Python requests: HTTPSConnectionPool(host='api.example.com', port=443): Max retries exceeded with url: /v1 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] ...')))
- DST Root CA X3 expired (old clients fail) Old clients: certificate has expired — Let's Encrypt chain uses expired DST Root CA X3 (OpenSSL 1.0.x, Android < 7.1.1)
- Keystore was tampered with, or password was incorrect Java keytool: java.io.IOException: Keystore was tampered with, or password was incorrect
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 18 Nov 2026