CVE-2012-0553 json
Buffer overflow in yaSSL, as used in MySQL 5.1.x before 5.1.68 and 5.5.x before 5.5.28, has unspecified impact and attack vectors, a differ…
published 2013-03-28 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-0585
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
Buffer overflow in yaSSL, as used in MySQL 5.1.x before 5.1.68 and 5.5.x before 5.5.28, has unspecified impact and attack vectors, a different vulnerability than CVE-2013-1492.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-0553 updated cvss 7.5
mysql: yaSSL buffer overflow ((a different flaw than CVE-2013-1492)
-
Red Hat Enterprise Linux 5 mysql Red Hat Enterprise Linux 6 mysql, mysql-libs, mysql-test, mysql-bench, mysql-server, mysql-embeddednot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.60% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
- Technology feeds
References
-
security.gentoo.org
/glsa/glsa-201308-06.xml
vendor-advisory
-
secunia.com
/advisories/52445
third-party-advisory, vendor-advisory
- dev.mysql.com /doc/relnotes/mysql/5.1/en/news-5-1-68.html
-
secunia.com
/advisories/53372
third-party-advisory
- blogs.oracle.com /sunsecurity/entry/cve_2012_0553_buffer_overflow
Sources
- CVE List CVE-2012-0553
- NVD CVE-2012-0553
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.