Skip to content
Noroxi
NVD / CVE Program· CNA openssl

CVE-2017-3737: OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism.

MediumCVSS 5.9 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Plan (action score 47/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 78.6% (FIRST EPSS); higher than 99.5% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: openssl (Alpine:v3.3) 1.0.2n-r0; openssl (Debian:12) 1.1.0b-2; openssl1.0 (Debian:9) 1.0.2l-2+deb9u2.

Add it to your regular patch cycle. Upgrade to openssl (Alpine:v3.3) 1.0.2n-r0; openssl (Debian:12) 1.1.0b-2; openssl1.0 (Debian:9) 1.0.2l-2+deb9u2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism. The intent was that if a fatal error occurred during a handshake then OpenSSL would move into the error state and would immediately fail if you attempted to continue the handshake. This works as designed for the explicit handshake functions (SSL_do_handshake(), SSL_accept() and SSL_connect()), however due to a bug it does not work correctly if SSL_read() or SSL_write() is called directly. In that scenario, if the handshake fails then a fatal error will be returned in the initial function call. If SSL_read()/SSL_write() is subsequently called by the application for the same SSL object then it will succeed and the data is passed without being decrypted/encrypted directly from the SSL/TLS record layer. In order to exploit this issue an application bug would have to be present that resulted in a call to SSL_read()/SSL_write() being issued after having already received a fatal error. OpenSSL version 1.0.2b-1.0.2m are affected. Fixed in OpenSSL 1.0.2n. OpenSSL 1.1.0 is not affected.

Published
Dec 7, 2017
Updated
Jun 16, 2026
EPSS
78.6% · 99th percentile

Report tools

JSON

Action score

47

Plan

Add it to your regular patch cycle.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
24 / 30 · 78.6%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2017-3737

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Check your server's TLS configurationRun the SSL check

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Check your server's TLS configurationRun the SSL check

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
opensslopenssl
debiandebian linux

Check your server's TLS configuration

The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.

Run the SSL check

Versions reported by the vendor

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

  • OpenSSL Software Foundation OpenSSL

    • 1.0.2b-1.0.2maffected

Package-level exposure

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

EcosystemPackageAffected rangeFix
Alpine:v3.3opensslbefore 1.0.2n-r01.0.2n-r0
Debian:12opensslbefore 1.1.0b-21.1.0b-2
Debian:9openssl1.0before 1.0.2l-2+deb9u21.0.2l-2+deb9u2
openSUSE:Tumbleweedopenssl-1_0_0before 1.0.2u-6.21.0.2u-6.2
Red Hat:enterprise_linux:7::clientopensslbefore 1:1.0.2k-12.el71:1.0.2k-12.el7
Red Hat:enterprise_linux:7::clientopenssl-debuginfobefore 1:1.0.2k-12.el71:1.0.2k-12.el7
Red Hat:enterprise_linux:7::clientopenssl-develbefore 1:1.0.2k-12.el71:1.0.2k-12.el7
Red Hat:enterprise_linux:7::clientopenssl-libsbefore 1:1.0.2k-12.el71:1.0.2k-12.el7
Red Hat:enterprise_linux:7::clientopenssl-perlbefore 1:1.0.2k-12.el71:1.0.2k-12.el7
Red Hat:enterprise_linux:7::clientopenssl-staticbefore 1:1.0.2k-12.el71:1.0.2k-12.el7
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apache-commons-daemonbefore 0:1.1.0-1.redhat_2.1.jbcs.el60:1.1.0-1.redhat_2.1.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apache-commons-daemon-jsvcbefore 1:1.1.0-1.redhat_2.jbcs.el61:1.1.0-1.redhat_2.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apache-commons-daemon-jsvc-debuginfobefore 1:1.1.0-1.redhat_2.jbcs.el61:1.1.0-1.redhat_2.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-aprbefore 0:1.6.3-14.jbcs.el60:1.6.3-14.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-debuginfobefore 0:1.6.3-14.jbcs.el60:1.6.3-14.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-develbefore 0:1.6.3-14.jbcs.el60:1.6.3-14.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-utilbefore 0:1.6.1-9.jbcs.el60:1.6.1-9.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-debuginfobefore 0:1.6.1-9.jbcs.el60:1.6.1-9.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-develbefore 0:1.6.1-9.jbcs.el60:1.6.1-9.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-ldapbefore 0:1.6.1-9.jbcs.el60:1.6.1-9.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-mysqlbefore 0:1.6.1-9.jbcs.el60:1.6.1-9.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-nssbefore 0:1.6.1-9.jbcs.el60:1.6.1-9.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-odbcbefore 0:1.6.1-9.jbcs.el60:1.6.1-9.jbcs.el6
Red Hat:jboss_core_services:1::el6jbcs-httpd24-apr-util-opensslbefore 0:1.6.1-9.jbcs.el60:1.6.1-9.jbcs.el6

+85

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

Published before and after this one in the same product

  • ← EarlierCVE-2017-3736Nov 2, 2017 · There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL before 1.0.2m and 1.1.0 before 1.1.0g.
    29Monitor
  • ← EarlierCVE-2016-8610Nov 13, 2017 · 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…
    42Plan
  • Later →CVE-2017-3738Dec 7, 2017 · There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli.
    27Monitor

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
alpine:openssl1.0.2n-r0 · Alpine:v3.3Package registry (OSV)
debian:openssl1.1.0b-2 · Debian:12Package registry (OSV)
debian:openssl1.01.0.2l-2+deb9u2 · Debian:9Package registry (OSV)
opensuse:openssl-1_0_01.0.2u-6.2 · openSUSE:TumbleweedPackage registry (OSV)
red hat:jbcs-httpd24-apache-commons-daemon0:1.1.0-1.redhat_2.1.jbcs.el7 · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-apache-commons-daemon-jsvc1:1.1.0-1.redhat_2.jbcs.el7 · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-apache-commons-daemon-jsvc-debuginfo1:1.1.0-1.redhat_2.jbcs.el7 · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-apr0:1.6.3-14.jbcs.el7 · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-apr-debuginfo0:1.6.3-14.jbcs.el7 · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-apr-devel0:1.6.3-14.jbcs.el7 · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:openssl1:1.0.2k-12.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:openssl-debuginfo1:1.0.2k-12.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:openssl-devel1:1.0.2k-12.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:openssl-libs1:1.0.2k-12.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:openssl-perl1:1.0.2k-12.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:openssl-static1:1.0.2k-12.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
suse:openssl1.0.2j-60.20.2 · SUSE:Linux Enterprise Desktop 12 SP2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

Patch and commit links

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

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

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.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

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

nvd-primary

Attack context

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

ATT&CK techniques

—

References

All records