OpenSSL 1.0.1/1.0.2/1.1.0 64-bit Block Cipher SWEET32 information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.27 |
Summary
A vulnerability identified as critical has been detected in OpenSSL 1.0.1/1.0.2/1.1.0. This affects an unknown part of the component 64-bit Block Cipher. Performing a manipulation results in information disclosure (SWEET32). This vulnerability is cataloged as CVE-2016-2183. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
Details
A vulnerability, which was classified as critical, was found in OpenSSL 1.0.1/1.0.2/1.1.0 (Network Encryption Software). This affects some unknown functionality of the component 64-bit Block Cipher. The manipulation with an unknown input leads to a information disclosure vulnerability (SWEET32). 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 weakness was shared 08/24/2016 as SWEET32 as confirmed blog post (Website). It is possible to read the advisory at openssl.org. The vendor was not involved in the public release. This vulnerability is uniquely identified as CVE-2016-2183. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK. The advisory points out:
Because DES (and triple-DES) has only a 64-bit block size, birthday attacks are a real concern. With the ability to run Javascript in a browser, it is possible to send enough traffic to cause a collision, and then use that information to recover something like a session Cookie. Their experiments have been able to recover a cookie in under two days. More details are available at their website. But the take-away is this: triple-DES should now be considered as “bad” as RC4.
It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 95255 (AIX OpenSSL Advisory : openssl_advisory21.asc (SWEET32)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family AIX Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 157837 (Oracle Enterprise Linux Security Update for python (ELSA-2018-3041)). The advisory illustrates:
Triple-DES, which shows up as “DES-CBC3” in an OpenSSL cipher string, is still used on the Web, and major browsers are not yet willing to completely disable it.
The blog post contains the following remark:
For 1.0.2 and 1.0.1, we removed the triple-DES ciphers from the “HIGH” keyword and put them into “MEDIUM.” Note that we did not remove them from the “DEFAULT” keyword. For the 1.1.0 release, which we expect to release tomorrow, we will treat triple-DES just like we are treating RC4. It is not compiled by default; you have to use “enable-weak-ssl-ciphers” as a config option. Even when those ciphers are compiled, triple-DES is only in the “MEDIUM” keyword. In addition, because this is a new release, we also removed it from the “DEFAULT” keyword.
The vulnerability is also documented in the databases at Tenable (95255), SecurityFocus (BID 92630†) and SecurityTracker (ID 1036696†). Further details are available at sweet32.info. The entries VDB-90396, VDB-90937, VDB-90940 and VDB-90941 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- HPE Business Service Management
Product
Type
Name
Version
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.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.6
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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
Name: SWEET32Class: Information disclosure / SWEET32
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 95255
Nessus Name: AIX OpenSSL Advisory : openssl_advisory21.asc (SWEET32)
Nessus File: 🔍
Nessus Family: 🔍
OpenVAS ID: 59958
OpenVAS Name: RedHat Update for openssl RHSA-2016:1940-01
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/29/2016 🔍08/24/2016 🔍
08/25/2016 🔍
08/26/2016 🔍
08/31/2016 🔍
04/01/2025 🔍
Sources
Product: openssl.orgAdvisory: SWEET32
Status: Confirmed
CVE: CVE-2016-2183 (🔍)
GCVE (CVE): GCVE-0-2016-2183
GCVE (VulDB): GCVE-100-90939
SecurityFocus: 92630
SecurityTracker: 1036696 - OpenSSL 3DES Cipher Block Collision Weakness Lets Remote Users Decrypt Data in Certain Cases
scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
See also: 🔍
Entry
Created: 08/25/2016 14:36Updated: 04/01/2025 01:29
Changes: 08/25/2016 14:36 (55), 02/20/2017 08:12 (22), 09/14/2022 10:00 (5), 09/14/2022 10:04 (11), 04/01/2025 01:29 (15)
Complete: 🔍
Cache ID: 216:7AB:103
Submit
Duplicate
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.