Skip to content
Noroxi
CVE-2016-8610· NVD / CVE Program· CNA redhat

A denial of service flaw was found in OpenSSL 0.9.8, 1.0.1, 1.0.2 through 1.0.2h, and 1.1.0 in the way the TLS/SSL protocol defined processi

A denial of service flaw was found in OpenSSL 0.9.8, 1.0.1, 1.0.2 through 1.0.2h, and 1.1.0 in the way the TLS/SSL protocol defined processing of ALERT packets during a connection handshake. A remote attacker could use this flaw to make a TLS/SSL server consume an excessive amount of CPU and fail to accept connections from other clients.

HighCVSS 7.5 · v3.1—Proof of concept Fix available
Published
Nov 13, 2017
Updated
Jun 16, 2026
EPSS
39.7% · 99th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

42

Plan

Add it to your regular patch cycle.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
12 / 30 · 39.7%

Affected systems

VendorProduct
opensslopenssl
debiandebian linux
redhatenterprise linux desktop
redhatenterprise linux server
redhatenterprise linux server aus
redhatenterprise linux server eus
redhatenterprise linux server tus
redhatenterprise linux workstation
redhatjboss enterprise application platform
redhatenterprise linux
netappcn1610 firmware
netappcn1610

and 41 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • paloaltonetworks pan-osup to 6.1.17 inclusive
  • paloaltonetworks pan-os7.0.0 and later · up to 7.0.15 inclusive
  • paloaltonetworks pan-os7.1.0 and later · up to 7.1.10 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • OpenSSL OpenSSL

    • All 0.9.8, All 1.0.1, 1.0.2 through 1.0.2h, 1.1.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12opensslbefore 1.0.2j-11.0.2j-1
Debian:7opensslbefore 1.0.1t-1+deb7u21.0.1t-1+deb7u2
Debian:8opensslbefore 1.0.1t-1+deb8u61.0.1t-1+deb8u6
openSUSE:Tumbleweedgnutlsbefore 3.7.2-1.23.7.2-1.2
Red Hat:enterprise_linux:6::clientgnutlsbefore 0:2.12.23-21.el60:2.12.23-21.el6
Red Hat:enterprise_linux:6::clientgnutls-debuginfobefore 0:2.12.23-21.el60:2.12.23-21.el6
Red Hat:enterprise_linux:6::clientgnutls-develbefore 0:2.12.23-21.el60:2.12.23-21.el6
Red Hat:enterprise_linux:6::clientgnutls-guilebefore 0:2.12.23-21.el60:2.12.23-21.el6
Red Hat:enterprise_linux:6::clientgnutls-utilsbefore 0:2.12.23-21.el60:2.12.23-21.el6
Red Hat:enterprise_linux:6::clientopensslbefore 0:1.0.1e-48.el6_8.40:1.0.1e-48.el6_8.4
Red Hat:enterprise_linux:6::clientopenssl-debuginfobefore 0:1.0.1e-48.el6_8.40:1.0.1e-48.el6_8.4
Red Hat:enterprise_linux:6::clientopenssl-develbefore 0:1.0.1e-48.el6_8.40:1.0.1e-48.el6_8.4
Red Hat:enterprise_linux:6::clientopenssl-perlbefore 0:1.0.1e-48.el6_8.40:1.0.1e-48.el6_8.4
Red Hat:enterprise_linux:6::clientopenssl-staticbefore 0:1.0.1e-48.el6_8.40:1.0.1e-48.el6_8.4
Red Hat:enterprise_linux:7::clientopensslbefore 1:1.0.1e-60.el7_3.11:1.0.1e-60.el7_3.1
Red Hat:enterprise_linux:7::clientopenssl-debuginfobefore 1:1.0.1e-60.el7_3.11:1.0.1e-60.el7_3.1
Red Hat:enterprise_linux:7::clientopenssl-develbefore 1:1.0.1e-60.el7_3.11:1.0.1e-60.el7_3.1
Red Hat:enterprise_linux:7::clientopenssl-libsbefore 1:1.0.1e-60.el7_3.11:1.0.1e-60.el7_3.1
Red Hat:enterprise_linux:7::clientopenssl-perlbefore 1:1.0.1e-60.el7_3.11:1.0.1e-60.el7_3.1
Red Hat:enterprise_linux:7::clientopenssl-staticbefore 1:1.0.1e-60.el7_3.11:1.0.1e-60.el7_3.1
Red Hat:jboss_core_services:1::el6jbcs-httpd24-httpdbefore 0:2.4.23-120.jbcs.el60:2.4.23-120.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-httpd-debuginfobefore 0:2.4.23-120.jbcs.el60:2.4.23-120.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-httpd-develbefore 0:2.4.23-120.jbcs.el60:2.4.23-120.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-httpd-libsbefore 0:2.4.23-120.jbcs.el60:2.4.23-120.jbcs.el6

+96

Other highest-scoring records for the same primary product.

  • CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This week
  • CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code
    65This week
  • CVE-2016-2108The ASN.1 implementation in OpenSSL before 1.0.1o and 1.0.2 before 1.0.2c allows remote attackers to execute arbitrary code or cause a denia
    62This week
  • CVE-2016-6309statem/statem.c in OpenSSL 1.1.0a does not consider memory-block movement after a realloc call, which allows remote attackers to cause a den
    60This week
  • CVE-2022-3786X.509 Email Address Variable Length Buffer Overflow
    58Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:openssl1.0.2j-1 · Debian:12Package registry (OSV)
opensuse:gnutls3.7.2-1.2 · openSUSE:TumbleweedPackage registry (OSV)
red hat:gnutls0:2.12.23-21.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:gnutls-debuginfo0:2.12.23-21.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:gnutls-devel0:2.12.23-21.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:gnutls-guile0:2.12.23-21.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:gnutls-utils0:2.12.23-21.el6 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:jbcs-httpd24-httpd0:2.4.23-120.jbcs.el7 · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:openssl0:1.0.1e-48.el6_8.4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:openssl-debuginfo0:1.0.1e-48.el6_8.4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:openssl-devel0:1.0.1e-48.el6_8.4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:openssl-libs1:1.0.1e-60.el7_3.1 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:openssl-perl0:1.0.1e-48.el6_8.4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:openssl-static0:1.0.1e-48.el6_8.4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
suse:compat-openssl097g0.9.7g-146.22.50.1 · SUSE:Linux Enterprise Server for SAP Applications 11 SP4Package registry (OSV)
suse:compat-openssl0980.9.8j-105.1 · SUSE:Linux Enterprise Desktop 12 SP1Package registry (OSV)
suse:gnutls2.4.1-24.39.67.1 · SUSE:Linux Enterprise Software Development Kit 11 SP4Package registry (OSV)
suse:openssl1.0.1i-54.5.1 · SUSE:Linux Enterprise Desktop 12 SP1Package registry (OSV)
suse:openssl11.0.1g-0.57.1 · SUSE:Linux Enterprise Server 11-SECURITYPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:332016-12-27

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-322 d
  2. Published
  3. TodaySep 30, 2026+3242 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
function expand(node) {  return node.children.map(expand);}

Fixed

ts
const MAX_DEPTH = 32;function expand(node, depth = 0) {  if (depth > MAX_DEPTH) throw new Error("too deep");  return node.children.map((c) => expand(c, depth + 1));}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records