SSL/TLS Vulnerability Database

Search known SSL/TLS vulnerabilities and CVEs

Searching vulnerability database...

Found vulnerabilities

About

The SSL/TLS Vulnerability Database provides a comprehensive catalog of known vulnerabilities affecting SSL/TLS implementations, including protocol-level flaws, implementation bugs, and cryptographic weaknesses. Each vulnerability entry includes detailed technical descriptions, affected software versions, CVSS severity scores, remediation guidance, and detection methods.

The database covers critical vulnerabilities from Heartbleed (CVE-2014-0160) and POODLE (CVE-2014-3566) to newer threats like Raccoon (CVE-2020-1968) and HoneyBadger (CVE-2021-3449). Use this resource to understand which vulnerabilities affect your infrastructure, verify that your systems are patched, and stay informed about emerging SSL/TLS security threats as they are discovered.

How to Use

1Browse the vulnerability database by category, severity, or affected software
2Click on any vulnerability entry to view full technical details and remediation steps
3Use the search function to find specific CVEs or vulnerability names
4Check if your server is vulnerable by testing with the linked detection tools

Use Cases

•Vulnerability Assessment: Identify which SSL/TLS vulnerabilities may affect your servers and prioritize patching based on severity and exploitability
•Incident Response: Quickly research newly disclosed vulnerabilities to understand impact and determine if your systems are affected
•Patch Validation: Verify that security patches have been correctly applied by testing for known vulnerabilities
•Security Training: Use the database as a learning resource for understanding SSL/TLS attack vectors and defensive measures
•Audit Documentation: Reference specific CVEs and their remediation status for security audit reports and compliance documentation

Tips & Best Practices

•Subscribe to CVE alerts for SSL/TLS vulnerabilities to stay informed about new discoveries
•Test for critical vulnerabilities immediately when new CVEs are disclosed — especially remote code execution flaws
•Keep all SSL/TLS libraries (OpenSSL, NSS, BoringSSL) updated to the latest patched versions
•Use the vulnerability database to create a prioritized patching schedule based on CVSS scores

Technical Details

●CVE Coverage: Comprehensive database of SSL/TLS CVEs from 2014 to present with CVSS v3.1 scoring

●Categories: Protocol vulnerabilities, implementation bugs, cryptographic weaknesses, side-channel attacks

●Severity Levels: Critical (9.0-10.0), High (7.0-8.9), Medium (4.0-6.9), Low (0.1-3.9)

● Detection Methods: Links to detection tools and test scripts for each vulnerability

Frequently Asked Questions

The database is updated whenever new SSL/TLS vulnerabilities are disclosed, typically within 24-48 hours of public disclosure. Critical vulnerabilities with active exploits are added immediately. The database also receives monthly updates to add newly assigned CVEs and update remediation information for existing entries.

Prioritize by CVSS score and exploitability: Heartbleed (CVE-2014-0160) and other remote code execution flaws first, followed by padding oracle attacks (POODLE, Lucky 13), then downgrade attacks (FREAK, Logjam), and finally information disclosure vulnerabilities. Always patch critical and high-severity issues within 24-72 hours.

Use the detection method linked in each vulnerability entry, or run the SSL Scanner tool which checks for known vulnerabilities automatically. The scanner tests your server against all entries in the vulnerability database and reports any matches. For library-specific vulnerabilities, check your server's OpenSSL or NSS version against the affected versions listed.