BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2017
CVE-2017-3737High confidence

OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism

OpenSSL Software Foundation · OpenSSL

Official source article: Red Hat RHSA-2018:2185 ↗. Check the applicable product and release in the original source.

5.9MediumCVSS 3.0
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:High, raised one band.upgradedsince 22 Oct 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 78.67% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs OpenSSL Software Foundation OpenSSL and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.1.1.0b-2Debian Security Tracker ↗Source updated 22 Oct 2026
Debian bookwormbookworm · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.1.1.0b-2Debian Security Tracker ↗Source updated 22 Oct 2026
Debian forkyforky · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.1.1.0b-2Debian Security Tracker ↗Source updated 22 Oct 2026
Debian sidsid · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.1.1.0b-2Debian Security Tracker ↗Source updated 22 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current · 1 archived
SSA-179516 · CSAF 2.0 · revision 8 · finalSiemens ProductCERTCVE-2017-3737
20 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • MindConnect IoT2040
  • MindConnect Nano (IPC227D)
  • SIMATIC ET 200SP Open Controller CPU 1515SP PC (incl. SIPLUS variants)
  • SIMATIC HMI WinCC Flexible
  • SIMATIC IPC DiagBase
  • SIMATIC IPC DiagMonitor
  • SIMATIC S7-1200 CPU family (incl. SIPLUS variants)
  • SIMATIC S7-1500 CPU family (incl. related ET200 CPUs and SIPLUS variants)
  • SIMATIC S7-1500 Software Controller
  • SIMATIC STEP 7 (TIA Portal) V13
  • SIMATIC STEP 7 (TIA Portal) V14
  • SIMATIC STEP 7 (TIA Portal) V15
Summary
In OpenSSL 1.0.2 an "error state" mechanism was introduced. This "error state" mechanism does not work correctly if SSL_read() or SSL_write() is called directly by an application. This could result in data being sent out unencrypted by the SSL/TLS record layer. Successful exploitation requires an attacker to cause a fatal error in the victim's SSL/TLS handshake algorithm, and that the targeted application calls SSL_read() or SSL_write() after having already received a fatal error. No user interaction or privileges are required to exploit this security vulnerability. The vulnerability could allow to compromise confidentiality of data by transmitting it unencrypted over the network.
Remediation
Update to V3.14 P021 or later version https://www.winccoa.com/downloads/category/versions- patches.html
CVE-2017-3737 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityopenssl: Read/write after SSL object in error stateNo longer in the provider’s current catalogue
3 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • openssl.src as a component of Red Hat JBoss Enterprise Application Platform 6
  • openssl.src as a component of Red Hat JBoss Enterprise Web Server 2
  • openssl.src as a component of Red Hat JBoss Web Server 3
Summary
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.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2017-12854

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Out-of-bounds Read → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-125
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0180Dell Data Protection Advisor: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Data Protection Advisor ausnutzen, um beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu erzeugen, Sicherheitsmaßnahmen zu umgehen und nicht näher spezifizierte Angriffe zu starten.

Official advisory ↗
BSI · German · WID-SEC-2023-1594IBM Tivoli Network Manager: Mehrere Schwachstellen

Ein entfernter, anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in IBM Tivoli Network Manager ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand herbeizuführen, seine Privilegien auszuweiten, Daten zu manipulieren, nicht spezifizierte Auswirkungen zu verursachen und einen Cross-Site-Scripting-Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-0205OpenSSL: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in OpenSSL ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV18-065Oracle Critical Patch update Advisory - April 2018

.3 Sun ZFS Storage Appliance Kit (AK), versions prior to 8.7.17 CVE References: CVE-2013-1768, CVE-2014-0054, CVE-2015-7501, CVE-2015-7940, CVE-2016-0635, CVE-2016-2177, CVE-2016-2178, CVE-2016-2179, CVE-2016-2180, CVE-2016-2181, CVE-2016-2182, CVE-2016-2183, CVE-2016-3092, CVE-2016-3506, CVE-2016-5007, CVE-2016-5019, CVE-2016-6302, CVE-2016-6303, CVE-2016-6304, CVE-2016-6305, CVE-2016-6306, CVE-2016-6307, CVE-2016-6308, CVE-2016-6309, CVE-2016-6814, CVE-2016-7052, CVE-2016-8745, CVE-2016-9878, CVE-2017-1039, CVE-2017-1040, CVE-2017-1261, CVE-2017-1307, CVE-2017-1308, CVE-2017-1509, CVE-2017-1570, CVE-2017-1756, CVE-2017-3735, CVE-2017-3736, CVE-2017-3737, CVE-2017-3738, CVE-2017-5645, CVE-2017-5662, CVE-2017-5664, CVE-2017-5715, CVE-2017-5753, CVE-2017-5754, CVE-2017-7525, CVE-2017-7674, CVE-2017-7805, CVE-2017-9798, CVE-2018-0739, CVE-2018-2563, CVE-2018-2572, CVE-2018-2587, CVE-2018-2628, CVE-2018-2718, CVE-2018-2737, CVE-2018-2738, CVE-2018-2739, CVE-2018-2742, CVE-2018-2746, CVE-2018-2747, CVE-2018-2748, CVE-2018-2749, CVE-2018-2750, CVE-2018-2752, CVE-2018-2753, CVE-2018-2754, CVE-2018-2755, CVE-2018-2756, CVE-2018-2758, CVE-2018-2759, CVE-2018-2760, CVE-2018-2761, CVE-2018-2762, CVE-2018-2763, CVE-2018-2764, CVE-2018-2765, CVE-2018-2766, CVE-2018-2768, CVE-2018-2769, CVE-2018-2770, CVE

Official advisory ↗
Canadian Centre for Cyber Security · English · AV18-012Oracle Critical Patch updates

704, CVE-2016-0800, CVE-2016-1181, CVE-2016-1182, CVE-2016-2105, CVE-2016-2106, CVE-2016-2107, CVE-2016-2109, CVE-2016-2177, CVE-2016-2178, CVE-2016-2179, CVE-2016-2180, CVE-2016-2181, CVE-2016-2182, CVE-2016-2183, CVE-2016-2518, CVE-2016-2550, CVE-2016-4449, CVE-2016-5385, CVE-2016-5387, CVE-2016-6302, CVE-2016-6303, CVE-2016-6304, CVE-2016-6305, CVE-2016-6306, CVE-2016-6307, CVE-2016-6308, CVE-2016-6309, CVE-2016-6814, CVE-2016-7052, CVE-2016-7055, CVE-2016-7977, CVE-2016-8735, CVE-2016-9878, CVE-2017-0781, CVE-2017-0782, CVE-2017-0783, CVE-2017-0785, CVE-2017-3730, CVE-2017-3731, CVE-2017-3732, CVE-2017-3733, CVE-2017-3735, CVE-2017-3736, CVE-2017-3737, CVE-2017-3738, CVE-2017-5461, CVE-2017-5645, CVE-2017-5664, CVE-2017-5715, CVE-2017-9072, CVE-2017-9798, CVE-2017-10068, CVE-2017-10262, CVE-2017-10273, CVE-2017-10282, CVE-2017-10301, CVE-2017-10352, CVE-2017-12617, CVE-2017-13077, CVE-2017-13078, CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082, CVE-2018-2560, CVE-2018-2561, CVE-2018-2562, CVE-2018-2564, CVE-2018-2565, CVE-2018-2566, CVE-2018-2567, CVE-2018-2568, CVE-2018-2569, CVE-2018-2570, CVE-2018-2571, CVE-2018-2573, CVE-2018-2574, CVE-2018-2575, CVE-2018-2576, CVE-2018-2577, CVE-2018-2578, CVE-2018-2579, CVE-2018-2580, CVE-2018-2581, CVE-2018-2582, CVE-2018-2583, CVE-2

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-267Multiples vulnérabilités dans Juniper Networks Junos Space

ERecord?id=CVE-2017-17807 Référence CVE CVE-2017-18190 https://www.cve.org/CVERecord?id=CVE-2017-18190 Référence CVE CVE-2017-18207 https://www.cve.org/CVERecord?id=CVE-2017-18207 Référence CVE CVE-2017-18258 https://www.cve.org/CVERecord?id=CVE-2017-18258 Référence CVE CVE-2017-18267 https://www.cve.org/CVERecord?id=CVE-2017-18267 Référence CVE CVE-2017-18551 https://www.cve.org/CVERecord?id=CVE-2017-18551 Référence CVE CVE-2017-2810 https://www.cve.org/CVERecord?id=CVE-2017-2810 Référence CVE CVE-2017-3735 https://www.cve.org/CVERecord?id=CVE-2017-3735 Référence CVE CVE-2017-3736 https://www.cve.org/CVERecord?id=CVE-2017-3736 Référence CVE CVE-2017-3737 https://www.cve.org/CVERecord?id=CVE-2017-3737 Référence CVE CVE-2017-3738 https://www.cve.org/CVERecord?id=CVE-2017-3738 Référence CVE CVE-2017-5130 https://www.cve.org/CVERecord?id=CVE-2017-5130 Référence CVE CVE-2017-5715 https://www.cve.org/CVERecord?id=CVE-2017-5715 Référence CVE CVE-2017-5992 https://www.cve.org/CVERecord?id=CVE-2017-5992 Référence CVE CVE-2017-6462 https://www.cve.org/CVERecord?id=CVE-2017-6462 Référence CVE CVE-2017-6463 https://www.cve.org/CVERecord?id=CVE-2017-6463 Référence CVE CVE-2017-6464 https://www.cve.org/CVERecord?id=CVE-2017-6464 Référence CVE CVE-2017-6519 https://www.cve.org/CVERecord?id=CVE-2017-6519 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2018-AVI-376Multiples vulnérabilités dans SCADA les produits Siemens

De multiples vulnérabilités ont été découvertes dans SCADA les produits Siemens. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2018-AVI-339Multiples vulnérabilités dans les produits Juniper

ord?id=CVE-2017-10198 Référence CVE CVE-2017-10295 https://www.cve.org/CVERecord?id=CVE-2017-10295 Référence CVE CVE-2017-10345 https://www.cve.org/CVERecord?id=CVE-2017-10345 Référence CVE CVE-2017-10355 https://www.cve.org/CVERecord?id=CVE-2017-10355 Référence CVE CVE-2017-10356 https://www.cve.org/CVERecord?id=CVE-2017-10356 Référence CVE CVE-2017-10388 https://www.cve.org/CVERecord?id=CVE-2017-10388 Référence CVE CVE-2017-12613 https://www.cve.org/CVERecord?id=CVE-2017-12613 Référence CVE CVE-2017-15896 https://www.cve.org/CVERecord?id=CVE-2017-15896 Référence CVE CVE-2017-3145 https://www.cve.org/CVERecord?id=CVE-2017-3145 Référence CVE CVE-2017-3737 https://www.cve.org/CVERecord?id=CVE-2017-3737 Référence CVE CVE-2017-5715 https://www.cve.org/CVERecord?id=CVE-2017-5715 Référence CVE CVE-2017-5753 https://www.cve.org/CVERecord?id=CVE-2017-5753 Référence CVE CVE-2017-5754 https://www.cve.org/CVERecord?id=CVE-2017-5754 Référence CVE CVE-2017-7407 https://www.cve.org/CVERecord?id=CVE-2017-7407 Référence CVE CVE-2017-8816 https://www.cve.org/CVERecord?id=CVE-2017-8816 Référence CVE CVE-2017-8817 https://www.cve.org/CVERecord?id=CVE-2017-8817 Référence CVE CVE-2017-8818 https://www.cve.org/CVERecord?id=CVE-2017-8818 Référence CVE CVE-2017-9502 https://www.cve.org/CVERecord?id=CVE-2017-9502 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2018-AVI-190Multiples vulnérabilités dans Oracle Virtualization

De multiples vulnérabilités ont été découvertes dans Oracle Virtualization. Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2018-AVI-191Multiples vulnérabilités dans Oracle MySQL

e provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à l'intégrité des données. Solution Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Oracle cpuapr2018-3678067 du 17 avril 2018 http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html Bulletin de sécurité Oracle cpuapr2018verbose-3678067 du 17 avril 2018 http://www.oracle.com/technetwork/security-advisory/cpuapr2018verbose-3678108.html#MSQL Référence CVE CVE-2016-9878 https://www.cve.org/CVERecord?id=CVE-2016-9878 Référence CVE CVE-2017-3737 https://www.cve.org/CVERecord?id=CVE-2017-3737 Référence CVE CVE-2018-2755 https://www.cve.org/CVERecord?id=CVE-2018-2755 Référence CVE CVE-2018-2758 https://www.cve.org/CVERecord?id=CVE-2018-2758 Référence CVE CVE-2018-2759 https://www.cve.org/CVERecord?id=CVE-2018-2759 Référence CVE CVE-2018-2761 https://www.cve.org/CVERecord?id=CVE-2018-2761 Référence CVE CVE-2018-2762 https://www.cve.org/CVERecord?id=CVE-2018-2762 Référence CVE CVE-2018-2766 https://www.cve.org/CVERecord?id=CVE-2018-2766 Référence CVE CVE-2018-2769 https://www.cve.org/CVERecord?id=CVE-2018-2769 Référence CVE CVE-2018-2771 https://www.cve.org/CVERecord?id=CVE-2018-2771 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2018-AVI-184Multiples vulnérabilités dans les produits Juniper

rg/CVERecord?id=CVE-2016-2550 Référence CVE CVE-2016-4470 https://www.cve.org/CVERecord?id=CVE-2016-4470 Référence CVE CVE-2016-4565 https://www.cve.org/CVERecord?id=CVE-2016-4565 Référence CVE CVE-2016-5696 https://www.cve.org/CVERecord?id=CVE-2016-5696 Référence CVE CVE-2016-5829 https://www.cve.org/CVERecord?id=CVE-2016-5829 Référence CVE CVE-2017-1000385 https://www.cve.org/CVERecord?id=CVE-2017-1000385 Référence CVE CVE-2017-3732 https://www.cve.org/CVERecord?id=CVE-2017-3732 Référence CVE CVE-2017-3735 https://www.cve.org/CVERecord?id=CVE-2017-3735 Référence CVE CVE-2017-3736 https://www.cve.org/CVERecord?id=CVE-2017-3736 Référence CVE CVE-2017-3737 https://www.cve.org/CVERecord?id=CVE-2017-3737 Référence CVE CVE-2017-3738 https://www.cve.org/CVERecord?id=CVE-2017-3738 Référence CVE CVE-2018-0016 https://www.cve.org/CVERecord?id=CVE-2018-0016 Référence CVE CVE-2018-0017 https://www.cve.org/CVERecord?id=CVE-2018-0017 Référence CVE CVE-2018-0018 https://www.cve.org/CVERecord?id=CVE-2018-0018 Référence CVE CVE-2018-0019 https://www.cve.org/CVERecord?id=CVE-2018-0019 Référence CVE CVE-2018-0020 https://www.cve.org/CVERecord?id=CVE-2018-0020 Référence CVE CVE-2018-0021 https://www.cve.org/CVERecord?id=CVE-2018-0021 Référence CVE CVE-2018-0022 https://www.cve.org/CVERecord?id=CVE-2018-0022 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2018-AVI-037Multiples vulnérabilités dans Oracle MySQL

et une atteinte à l'intégrité des données. Solution Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Oracle cpujan2018-3236630 du 16 janvier 2018 http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html Bulletin de sécurité Oracle cpujan2018verbose-3236630#MSQL du 16 janvier 2018 http://www.oracle.com/technetwork/security-advisory/cpujan2018verbose-3236630.html#MSQL Référence CVE CVE-2017-12617 https://www.cve.org/CVERecord?id=CVE-2017-12617 Référence CVE CVE-2017-3736 https://www.cve.org/CVERecord?id=CVE-2017-3736 Référence CVE CVE-2017-3737 https://www.cve.org/CVERecord?id=CVE-2017-3737 Référence CVE CVE-2018-2562 https://www.cve.org/CVERecord?id=CVE-2018-2562 Référence CVE CVE-2018-2565 https://www.cve.org/CVERecord?id=CVE-2018-2565 Référence CVE CVE-2018-2573 https://www.cve.org/CVERecord?id=CVE-2018-2573 Référence CVE CVE-2018-2576 https://www.cve.org/CVERecord?id=CVE-2018-2576 Référence CVE CVE-2018-2583 https://www.cve.org/CVERecord?id=CVE-2018-2583 Référence CVE CVE-2018-2585 https://www.cve.org/CVERecord?id=CVE-2018-2585 Référence CVE CVE-2018-2586 https://www.cve.org/CVERecord?id=CVE-2018-2586 Référence CVE CVE-2018-2590 https://www.cve.org/CVERecord?id=CVE-2018-2590 Ré

Official advisory ↗
CERT-FR · French · CERTFR-2017-AVI-452Multiples vulnérabilités dans OpenSSL

De multiples vulnérabilités ont été découvertes dans OpenSSL . Elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-011526Node.js における脆弱性

Node.js には、不特定の脆弱性が存在します。 本脆弱性は、CVE-2017-3737 と関連する問題です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-011252OpenSSL における脆弱性

OpenSSL には、1024-bit 係数を伴う累乗法で使用される AVX2 Montgomery 乗算手順にオーバーフローの問題があるため、不特定の影響を受ける脆弱性が存在します。 本脆弱性は、CVE-2017-3736、CVE-2017-3732 および CVE-2015-3193 と類似した問題です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-010767OpenSSL における脆弱性

OpenSSL の "エラー状態 (error state)" メカニズムは、SSL_read() または SSL_write() 関数が直接呼び出された場合、正しく動作しないため、不特定の影響を受ける脆弱性が存在します。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-4821OpenSSL 신규 취약점 보안 업데이트 권고

정보노출이 발생하는 취약점(CVE-2017-3737)

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 7 Dec 2017 · Last source change 17 Sept 2024, 03:53 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2017-12854
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2017-3737 to advisory no longer present in the provider's current catalogue.
    Before
    remediation: access.redhat.com/CVE-2017-3737
    After
    advisory no longer present in the provider's current catalogue
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    1.0.2b-1.0.2m · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    1.0.2b-1.0.2m · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  3. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  4. ENISA EUVD mappingEUVD-2017-12854 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2017-12854"}
    ENISA EUVD ↗
  5. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: openssl.org/20171207.txt; removed vendor advisory: access.redhat.com/RHSA-2018:0998; removed vendor advisory: access.redhat.com/RHSA-2018:2185; 5 further removals.
    Before
    vendor advisory: access.redhat.com/RHSA-2018:0998 · vendor advisory: access.redhat.com/RHSA-2018:2185 · vendor advisory: access.redhat.com/RHSA-2018:2186 · 4 more references
    After
    vendor advisory: openssl.org/20171207.txt
    openssl.org ↗
  6. SeveritySeverity changed from Unknown to Medium.
    Before
    Unknown
    After
    Medium
    NIST NVD ↗
  7. CVSS scoreCVSS score changed from not recorded to 5.9 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).
    Before
    not recorded
    After
    5.9 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)
    NIST NVD ↗
  8. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
  9. Remediation statusRemediation status changed from Patch available to Mitigation available.
    Before
    Patch available
    After
    Mitigation available
    Canadian Centre for Cyber Security ↗
  10. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Canadian Centre for Cyber Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Remediation guidance recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2017-12854↗Vendor CSAF · Siemens ProductCERT↗Canadian Centre for Cyber Security remediation guidance↗Red Hat Product Security security advisory↗Vendor advisory↗CVE authority or vendor reference · Red Hat RHSA-2018:2185↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2017-3737 · cve.blacktree.nl