ROBOT attack (CVE-2017-13099): vulnerable RSA key exchange implementation
A scanner reports that the TLS stack leaks information through RSA PKCS#1 padding errors (Return Of Bleichenbacher's Oracle Threat).
ROBOT attack vulnerableReturn Of Bleichenbacher's Oracle ThreatROBOT VULNERABLE (weak oracle)RSA Padding Oracle ROBOT Meaning
Update the TLS library/appliance firmware (F5, Citrix, Cisco ACE and others were affected), and disable RSA key-exchange cipher suites (use ECDHE). Reissue is not required, but keys are protected by removing the RSA suites.
Common causes
- Vulnerable appliance firmware
- RSA key-exchange suites enabled
- Old OpenSSL/NSS/WolfSSL versions
- Load balancer not patched
- Default cipher lists
⚡ Quick fix
- Patch the device/library
- Remove
TLS_RSA_*suites - Rescan after the change
Detailed fix by platform
Shell
testssl.sh --robot example.com:443
How to diagnose
- Firmware — Patched?
- RSA suites — Disabled?
- Rescan — Clean?
🔧 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
- ACM region CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia)
- Django Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port)
- dual certs nginx dual RSA + ECDSA certificate setup fails (wrong order, unsupported ssl_certificate lines)
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