OpenSSL up to 0.9.8x access control ⚔ [Disputed]

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$5k-$25k0.00

Summaryinfo

A vulnerability was found in OpenSSL up to 0.9.8x. It has been classified as problematic. This affects an unknown function. This manipulation causes access control. This vulnerability appears as CVE-2011-1473. There is no available exploit. There is ongoing doubt regarding the real existence of this vulnerability.

Detailsinfo

A vulnerability classified as problematic was found in OpenSSL up to 0.9.8x (Network Encryption Software). Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect availability. The summary by CVE is:

** DISPUTED ** OpenSSL before 0.9.8l, and 0.9.8m through 1.x, does not properly restrict client-initiated renegotiation within the SSL and TLS protocols, which might make it easier for remote attackers to cause a denial of service (CPU consumption) by performing many renegotiations within a single connection, a different vulnerability than CVE-2011-5094. NOTE: it can also be argued that it is the responsibility of server deployments, not a security library, to prevent or limit renegotiation when it is inappropriate within a specific environment.

The issue has been introduced in 03/25/2009. The weakness was presented 06/16/2012 as Bug 707065 as not defined bug report (Bugzilla). It is possible to read the advisory at bugzilla.redhat.com. This vulnerability is known as CVE-2011-1473. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/07/2024). The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 1179 days. During that time the estimated underground price was around $5k-$25k. The real existence of this vulnerability is still doubted at the moment. The vulnerability scanner Nessus provides a plugin with the ID 68913 (Juniper Junos SSL/TLS Renegotiation DoS (JSA10580)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Junos Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 166626 (SUSE Enterprise Linux Security Update for lighttpd (SUSE-SU-2014:0050-1)).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Tenable (68913) and Vulnerability Center (SBV-31452†). See VDB-61004 for similar entry. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

Support

  • end of life (old version)

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 68913
Nessus Name: Juniper Junos SSL/TLS Renegotiation DoS (JSA10580)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍
ISS Proventia IPS: 🔍
PaloAlto IPS: 🔍

Timelineinfo

03/25/2009 🔍
03/13/2011 +718 days 🔍
03/21/2011 +7 days 🔍
05/15/2011 +55 days 🔍
06/16/2012 +398 days 🔍
06/16/2012 +0 days 🔍
07/16/2013 +395 days 🔍
03/23/2015 +615 days 🔍
08/07/2024 +3424 days 🔍

Sourcesinfo

Product: openssl.org

Advisory: Bug 707065
Status: Not defined
Disputed: 🔍

CVE: CVE-2011-1473 (🔍)
GCVE (CVE): GCVE-0-2011-1473
GCVE (VulDB): GCVE-100-61003

OVAL: 🔍
IAVM: 🔍

SecurityFocus: 48626
Vulnerability Center: 31452 - TLS/SSL Connections Renegotiation Allows Remote DoS, High

See also: 🔍

Entryinfo

Created: 03/23/2015 16:50
Updated: 08/07/2024 01:28
Changes: 03/23/2015 16:50 (63), 03/22/2017 09:54 (7), 12/04/2021 03:34 (3), 12/04/2021 03:43 (2), 08/07/2024 01:28 (16)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!