Oracle MySQL up to 5.5.20 memory corruption

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.
8.7$0-$5k0.00

Summaryinfo

A vulnerability was found in Oracle MySQL up to 5.5.20. It has been rated as critical. The impacted element is an unknown function. This manipulation causes memory corruption. This vulnerability is tracked as CVE-2012-0882. Moreover, an exploit is present.

Detailsinfo

A vulnerability classified as critical was found in Oracle MySQL up to 5.5.20 (Database Software). Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Buffer overflow in yaSSL, as used in MySQL 5.5.20 and possibly other versions including 5.5.x before 5.5.22 and 5.1.x before 5.1.62, allows remote attackers to execute arbitrary code via unspecified vectors, as demonstrated by VulnDisco Pack Professional 9.17. NOTE: as of 20120224, this disclosure has no actionable information. However, because the module author is a reliable researcher, the issue is being assigned a CVE identifier for tracking purposes. NOTE: due to lack of details, it is not clear whether this issue is a duplicate of CVE-2012-0492 or another CVE.

The weakness was disclosed 02/08/2012 with VulnDisco (Website). It is possible to read the advisory at blogs.oracle.com. The vendor was not involved in the public release. This vulnerability is known as CVE-2012-0882 since 01/19/2012. The exploitation appears to be difficult. The attack can be launched remotely. The successful exploitation requires a single authentication. Technical details are unknown but an exploit is available.

It is possible to download the exploit at partners.immunityinc.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 58661 (MySQL 5.5 < 5.5.22 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Databases. The commercial vulnerability scanner Qualys is able to test this issue with plugin 19857 (Oracle MySQL yaSSL Buffer Overflow Vulnerability (CVE-2012-0882)).

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 X-Force (80790), Tenable (58661), SecurityFocus (BID 51925†), OSVDB (78919†) and Secunia (SA47894†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.9
VulDB Meta Temp Score: 8.7

VulDB Base Score: 9.9
VulDB Temp Score: 8.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 58661
Nessus Name: MySQL 5.5 < 5.5.22 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/19/2012 🔍
02/08/2012 +20 days 🔍
02/09/2012 +1 days 🔍
02/09/2012 +0 days 🔍
02/09/2012 +0 days 🔍
02/24/2012 +15 days 🔍
03/05/2012 +10 days 🔍
04/11/2012 +37 days 🔍
12/21/2012 +254 days 🔍
01/15/2013 +25 days 🔍
01/02/2025 +4370 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: blogs.oracle.com
Organization: VulnDisco
Status: Not defined

CVE: CVE-2012-0882 (🔍)
GCVE (CVE): GCVE-0-2012-0882
GCVE (VulDB): GCVE-100-4627
X-Force: 80790 - Oracle MySQL yaSSL buffer overflow, High Risk
SecurityFocus: 51925 - MySQL 'yaSSL' Remote Code Execution Vulnerability
Secunia: 47894 - MySQL Unspecified Code Execution Vulnerability, Moderately Critical
OSVDB: 78919
SecurityTracker: 1026659 - MySQL Unspecified Flaw Lets Remote Users Execute Arbitrary Code
Vulnerability Center: 38045 - MySQL yaSSL Buffer Overflow Allows Remote Code Execution - CVE-2012-0882, High

scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 02/24/2012 01:00
Updated: 01/02/2025 18:40
Changes: 02/24/2012 01:00 (73), 04/23/2017 14:21 (4), 03/20/2021 18:21 (3), 01/02/2025 18:40 (18)
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 ▸

Interested in the pricing of exploits?

See the underground prices here!