Skip to content
Fencer Intel
medium 5.0

CVE-2011-3210 json

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 p…

published 2011-09-22 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3174

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.6%
EPSS 4.6% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

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.

Patch / fix

  • openssl Debian 14, Debian 13, Debian 12 1.0.0e-1

debian advisories DEBIAN-CVE-2011-3210

  • libqt4 SLES 12 SP1, SLES 12, SLED 12 SP1 +7 more 4.8.6-7.1
  • libqt4-sql-plugins SLES 12 SP1, SLES 12, SLED 12 SP1 +7 more 4.8.6-7.1

suse advisories SUSE-SU-403SUSE-SU-403 Forbidden-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-3210 updated cvss 5.0

openssl: TLS ephemeral ECDH crashes in OpenSSL

  • Red Hat Enterprise Linux 4 openssl, openssl096b Red Hat Enterprise Linux 5 openssl, openssl097a Red Hat Enterprise Linux 6 openssl, openssl098e, openssl-perl
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.56% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-399 Resource Management Errors
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.