Skip to content
Fencer Intel
medium 5.0

CVE-2013-0166 json

OpenSSL before 0.9.8y, 1.0.0 before 1.0.0k, and 1.0.1 before 1.0.1d does not properly perform signature verification for OCSP responses, wh…

published 13y ago modified 4mo ago also EUVD-2013-0205

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

Summary

OpenSSL before 0.9.8y, 1.0.0 before 1.0.0k, and 1.0.1 before 1.0.1d does not properly perform signature verification for OCSP responses, which allows remote OCSP servers to cause a denial of service (NULL pointer dereference and application crash) via an invalid key.

Patch / fix

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

debian advisories DEBIAN-CVE-2013-0166

  • openssl098 Ubuntu 14.04 LTS 0.9.8o-7ubuntu3.2.14.04.1

ubuntu advisories UBUNTU-CVE-2013-0166

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • rhev-hypervisor6 RHEL 6 6.4-20130306.2.el6_4
  • openssl RHEL 5 0.9.8e-26.el5_9.1
  • openssl RHEL 6 1.0.0-27.el6_4.2
  • openssl-perl RHEL 5 0.9.8e-26.el5_9.1
  • openssl-perl RHEL 6 1.0.0-27.el6_4.2

red hat advisories RHSA-2013:0636RHSA-2013:0587

  • 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

  • openssl-1_1 openSUSE Tumbleweed 1.1.1l-1.2

opensuse advisories openSUSE-SU-2024:11127-1

Is CVE-2013-0166 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2013-0166 updated cvss 5.0

openssl: DoS due to improper handling of OCSP response verification

  • Red Hat Enterprise Linux 5 openssl097a Red Hat Enterprise Linux 6 openssl098e Red Hat JBoss Enterprise Web Server 1 openssl
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux (v. 5 server) openssl 0.9.8e-26.el5_9.1, openssl-perl 0.9.8e-26.el5_9.1 Red Hat Enterprise Linux Desktop (v. 6) openssl 1.0.0-27.el6_4.2 Red Hat Enterprise Linux Desktop Optional (v. 6) openssl 1.0.0-27.el6_4.2, openssl-perl 1.0.0-27.el6_4.2 Red Hat Enterprise Linux HPC Node (v. 6) openssl 1.0.0-27.el6_4.2 Red Hat Enterprise Linux HPC Node Optional (v. 6) openssl 1.0.0-27.el6_4.2, openssl-perl 1.0.0-27.el6_4.2 Red Hat Enterprise Linux Server (v. 6) openssl 1.0.0-27.el6_4.2
    +3 more products
    Red Hat Enterprise Linux Server Optional (v. 6) openssl 1.0.0-27.el6_4.2, openssl-perl 1.0.0-27.el6_4.2 Red Hat Enterprise Linux Workstation (v. 6) openssl 1.0.0-27.el6_4.2 Red Hat Enterprise Linux Workstation Optional (v. 6) openssl 1.0.0-27.el6_4.2, openssl-perl 1.0.0-27.el6_4.2
    fixed: vendor fix RHSA-2013:0587
  • Red Hat JBoss Enterprise Application Platform 5.2
    fixed: vendor fix RHSA-2013:0783
  • Red Hat JBoss Enterprise Application Platform 6.1
    fixed: vendor fix RHSA-2013:0833
  • Red Hat JBoss Web Platform 5.2
    fixed: vendor fix RHSA-2013:0782
  • Red Hat JBoss Web Server 2.0
    fixed: vendor fix RHSA-2013:1013
  • Red Hat RHEV Hypervisor for RHEL-6 rhev-hypervisor6 6.4-20130306.2.el6_4
    fixed: vendor fix RHSA-2013:0636

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

19.65% chance of exploitation in the next 30 days, higher than 97% 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
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.