CVE-2012-5612: Heap-based buffer overflow in Oracle MySQL 5.5.19 and other versions through 5.5.28, and MariaDB 5.5.28a an...

Security readout for executives and security teams

This issue can let a logged-in MySQL or MariaDB user crash the database service, with possible code execution noted but not proven in the supplied sources. The main business risk is database outage or compromise where vulnerable 5.5-era servers still exist and accept authenticated connections. Exposure is most likely in legacy MySQL or MariaDB 5.5 deployments, especially internet-reachable databases, shared hosting, or applications with broad database users. Modern maintained versions are less likely affected, but source evidence does not enumerate every fixed release. Treat this as a legacy-system remediation priority. It is old, but public exploit material exists and database outages can be business-critical. Focus on finding forgotten vulnerable servers and upgrading or isolating them. Mitigation focus: Inventory MySQL and MariaDB servers, prioritizing 5.5-era deployments.; Apply vendor security updates from Oracle, MariaDB, and operating-system package advisories.; Restrict database network access to trusted application hosts only..

Prepared

Jun 24, 2026, 12:04 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.