| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OpenSSL 1.0.1/1.0.2. It has been classified as problematic. The impacted element is an unknown function of the component SHA512 Ticket Handler. The manipulation leads to denial of service. This vulnerability is documented as CVE-2016-6302. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, has been found in OpenSSL 1.0.1/1.0.2 (Network Encryption Software). This issue affects an unknown code block of the component SHA512 Ticket Handler. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability.
The weakness was released 09/22/2016 by Shi Lei as 20160922.txt as confirmed advisory (Website). The advisory is shared at openssl.org. The identification of this vulnerability is CVE-2016-6302 since 07/26/2016. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 351322 (Amazon Linux Security Advisory for openssl: AL2012-2018-245).
Upgrading to version 1.0.1u or 1.0.2i eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 92628†). Entries connected to this vulnerability are available at VDB-87879, VDB-88080, VDB-90937 and VDB-90940. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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
Class: Denial of serviceCWE: CWE-404
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 |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: OpenSSL 1.0.1u/1.0.2i
Patch: e97763c92c655dcf4af2860b3abd2bc4c8a267f9
Timeline
07/26/2016 🔍08/24/2016 🔍
09/22/2016 🔍
09/22/2016 🔍
09/23/2016 🔍
08/29/2024 🔍
Sources
Product: openssl.orgAdvisory: 20160922.txt
Researcher: Shi Lei
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-6302 (🔍)
GCVE (CVE): GCVE-0-2016-6302
GCVE (VulDB): GCVE-100-91901
SecurityFocus: 92628 - OpenSSL CVE-2016-6302 Denial of Service Vulnerability
SecurityTracker: 1036885
See also: 🔍
Entry
Created: 09/23/2016 18:11Updated: 08/29/2024 03:54
Changes: 09/23/2016 18:11 (48), 07/07/2019 16:32 (6), 09/20/2022 09:48 (4), 09/20/2022 09:53 (18), 08/29/2024 03:54 (16)
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.