CVE-2011-3210

CVE-2011-3210 is a medium-severity vulnerability in Openssl with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-399.

Key facts

Description

The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

Frequently asked questions

What is CVE-2011-3210?
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.
How severe is CVE-2011-3210?
CVE-2011-3210 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2011-3210 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (90th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2011-3210?
CVE-2011-3210 primarily affects Openssl. In total, 30 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2011-3210?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2011-3210 published?
CVE-2011-3210 was published on 2011-09-22 and last updated on 2026-06-16.

References

Affected products (30)

More vulnerabilities in Openssl

All CVEs affecting Openssl →

Other CWE-399 (Resource Management Errors) vulnerabilities

Browse all CWE-399 (Resource Management Errors) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: