OpenSSL up to 1.0.2l/1.1.0f x86_64 Montgomery Squaring bn_sqrx8x_internal information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in OpenSSL up to 1.0.2l/1.1.0f and classified as critical. This impacts the function bn_sqrx8x_internal of the component x86_64 Montgomery Squaring. Performing a manipulation results in information disclosure.
This vulnerability is cataloged as CVE-2017-3736. It is possible to initiate the attack remotely. There is no exploit available.
The affected component should be upgraded.
Details
A vulnerability classified as critical has been found in OpenSSL up to 1.0.2l/1.1.0f (Network Encryption Software). This affects the function bn_sqrx8x_internal of the component x86_64 Montgomery Squaring. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. This only affects processors that support the BMI1, BMI2 and ADX extensions like Intel Broadwell (5th generation) and later or AMD Ryzen.
The bug was discovered 01/30/2018. The weakness was shared 11/02/2017 by OSS-Fuzz (Website). The advisory is shared at openssl.org. This vulnerability is uniquely identified as CVE-2017-3736 since 12/16/2016. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 104639 (Tenable SecurityCenter OpenSSL 1.0.2 < 1.0.2m Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Misc. and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 38753 (NetApp Clustered Data ONTAP Multiple Vulnerabilities (NTAP-20171208-0001,NTAP-20180201-0001,NTAP-20171107-0002)).
Upgrading to version 1.0.2m or 1.1.0g eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (104639), SecurityFocus (BID 101666†) and SecurityTracker (ID 1039727†). The entries VDB-92314, VDB-92773, VDB-92782 and VDB-92786 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 1.0.2
- 1.0.2a
- 1.0.2b
- 1.0.2c
- 1.0.2d
- 1.0.2e
- 1.0.2f
- 1.0.2g
- 1.0.2h
- 1.0.2i
- 1.0.2j
- 1.0.2k
- 1.0.2l
- 1.1.0
- 1.1.0a
- 1.1.0b
- 1.1.0c
- 1.1.0d
- 1.1.0e
- 1.1.0f
License
Support
- end of life (old version)
Website
- Product: https://www.openssl.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 104639
Nessus Name: Tenable SecurityCenter OpenSSL 1.0.2 < 1.0.2m Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 53380
OpenVAS Name: Debian Security Advisory DSA 4018-1 (openssl - security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: OpenSSL 1.0.2m/1.1.0g
Patch: github.com
Timeline
12/16/2016 🔍08/28/2017 🔍
11/02/2017 🔍
11/02/2017 🔍
11/02/2017 🔍
11/02/2017 🔍
11/02/2017 🔍
11/16/2017 🔍
01/30/2018 🔍
01/05/2023 🔍
Sources
Product: openssl.orgAdvisory: RHSA-2018:0998
Researcher: OSS-Fuzz (OSS-Fuzz)
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-3736 (🔍)
GCVE (CVE): GCVE-0-2017-3736
GCVE (VulDB): GCVE-100-108909
OVAL: 🔍
SecurityFocus: 101666 - OpenSSL CVE-2017-3736 Information Disclosure Vulnerability
SecurityTracker: 1039727
See also: 🔍
Entry
Created: 11/02/2017 23:13Updated: 01/05/2023 14:36
Changes: 11/02/2017 23:13 (77), 12/02/2019 20:02 (9), 01/21/2021 15:39 (3), 01/05/2023 14:36 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.