Skip to content
Fencer Intel
medium 5.0

CVE-2011-1473 json

OpenSSL before 0.9.8l, and 0.9.8m through 1.x, does not properly restrict client-initiated renegotiation within the SSL and TLS protocols,…

published 2012-06-16 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1478

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

Summary

OpenSSL before 0.9.8l, and 0.9.8m through 1.x, does not properly restrict client-initiated renegotiation within the SSL and TLS protocols, which might make it easier for remote attackers to cause a denial of service (CPU consumption) by performing many renegotiations within a single connection, a different vulnerability than CVE-2011-5094. NOTE: it can also be argued that it is the responsibility of server deployments, not a security library, to prevent or limit renegotiation when it is inappropriate within a specific environment

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-1473 updated cvss 4.3

openssl: DoS via repeated SSL session renegotiations

  • Red Hat Enterprise Linux 4 openssl, openssl096b Red Hat Enterprise Linux 5 openssl, openssl097a Red Hat Enterprise Linux 6 openssl, openssl098e, openssl-perl
    affected: no fix planned “Will not fix”

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

66.87% chance of exploitation in the next 30 days, higher than 99.2% 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-264 Permissions, Privileges, and Access Controls
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.