Buffer overflow in MySQL
CVE-2012-0882
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.
Vulnerability class: Buffer Overflow
Published · last modified .
CVSS v2 metric
CVSS v2 base score 7.5 (High). Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P. This CVE predates CVSS v3 and has no v3 score from NVD.
EPSS exploit prediction
EPSS 0.053, 92.7th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- MySQL — versions 5.1.5, 5.1.23, 5.1.31
- Oracle MySQL — versions 5.5.0, 5.5.1, 5.5.2
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (retr0-13/cveScannerV2, scmanjarrez/CVEScannerV2). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- [Canvas] 20120223 VulnDisco MySQL 0day (mailing-list)
- [Canvas] 20120207 VulnDisco Pack Professional 9.17 (mailing-list)
- bugzilla.redhat.com/show_bug.cgi
- [oss-security] 20120224 Re: MySQL 0-day - does it need a CVE? (mailing-list)
- blogs.oracle.com/sunsecurity/entry/cve_2012_0882buffer_overflow_vulnerability (Vendor Advisory)