Skip to content
Fencer Intel
medium 5.0

CVE-2011-3207 json

crypto/x509/x509_vfy.c in OpenSSL 1.0.x before 1.0.0e does not initialize certain structure members, which makes it easier for remote attac…

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

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

Summary

crypto/x509/x509_vfy.c in OpenSSL 1.0.x before 1.0.0e does not initialize certain structure members, which makes it easier for remote attackers to bypass CRL validation by using a nextUpdate value corresponding to a time in the past.

Patch / fix

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

debian advisories DEBIAN-CVE-2011-3207

  • openssl RHEL 6 1.0.0-10.el6_1.5
  • openssl-perl RHEL 6 1.0.0-10.el6_1.5

red hat advisories RHSA-2011:1409

  • openssl-1_1 openSUSE Tumbleweed 1.1.1l-1.2

opensuse advisories openSUSE-SU-2024:11127-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-3207 updated cvss 4.3

openssl: CRL verification vulnerability

  • Red Hat Enterprise Linux Server (v. 6) openssl 1.0.0-10.el6_1.5 Red Hat Enterprise Linux Server Optional (v. 6) openssl 1.0.0-10.el6_1.5, openssl-perl 1.0.0-10.el6_1.5
    fixed: vendor fix RHSA-2011:1409
  • Red Hat Enterprise Linux 4 openssl, openssl096b Red Hat Enterprise Linux 5 openssl, openssl097a Red Hat Enterprise Linux 6 openssl098e
    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.36% 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:P/A:N

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.