# CVE-2012-5611: Memory corruption in n/a > Remote authenticated users can execute arbitrary code via a stack-based buffer overflow in the GRANT FILE command. - **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 3 Dec 2012 - **Updated:** 6 Aug 2024 - **Also known as:** CVE-2012-5579, GHSA-gcrp-g698-23xq, RHSA-2012:1551 ## What is CVE-2012-5611? CVE-2012-5611 is a medium-severity memory corruption vulnerability in Mariadb Mariadb, published on 3 Dec 2012. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Stack-based buffer overflow in the acl_get function in Oracle MySQL 5.5.19 and other versions through 5.5.28, and 5.1.53 and other versions through 5.1.66, and MariaDB 5.5.2.x before 5.5.28a, 5.3.x before 5.3.11, 5.2.x before 5.2.13 and 5.1.x before 5.1.66, allows remote authenticated users to execute arbitrary code via a long argument to the GRANT FILE command. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2012-5611? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mysql` | Red Hat:enterprise_linux:6::client | All versions | 0:5.1.66-2.el6_3 | | `mysql-bench` | Red Hat:enterprise_linux:6::client | All versions | 0:5.1.66-2.el6_3 | | `mysql-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:5.1.66-2.el6_3 | | `mysql-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:5.1.66-2.el6_3 | | `mysql-embedded` | Red Hat:enterprise_linux:6::client | All versions | 0:5.1.66-2.el6_3 | | `mysql-embedded-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:5.1.66-2.el6_3 | | `mysql-libs` | Red Hat:enterprise_linux:6::client | All versions | 0:5.1.66-2.el6_3 | | `mysql-server` | Red Hat:enterprise_linux:6::client | All versions | 0:5.1.66-2.el6_3 | | `mysql-test` | Red Hat:enterprise_linux:6::client | All versions | 0:5.1.66-2.el6_3 | | `mysql` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.1.66-2.el6_3 | | `mysql-bench` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.1.66-2.el6_3 | | `mysql-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.1.66-2.el6_3 | | `mysql-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.1.66-2.el6_3 | | `mysql-embedded` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.1.66-2.el6_3 | | `mysql-embedded-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.1.66-2.el6_3 | | `mysql-libs` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.1.66-2.el6_3 | | `mysql-server` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.1.66-2.el6_3 | | `mysql-test` | Red Hat:enterprise_linux:6::computenode | All versions | 0:5.1.66-2.el6_3 | | `mysql` | Red Hat:enterprise_linux:6::server | All versions | 0:5.1.66-2.el6_3 | | `mysql-bench` | Red Hat:enterprise_linux:6::server | All versions | 0:5.1.66-2.el6_3 | | `mysql-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:5.1.66-2.el6_3 | | `mysql-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:5.1.66-2.el6_3 | | `mysql-embedded` | Red Hat:enterprise_linux:6::server | All versions | 0:5.1.66-2.el6_3 | | `mysql-embedded-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:5.1.66-2.el6_3 | | `mysql-libs` | Red Hat:enterprise_linux:6::server | All versions | 0:5.1.66-2.el6_3 | | `mysql-server` | Red Hat:enterprise_linux:6::server | All versions | 0:5.1.66-2.el6_3 | | `mysql-test` | Red Hat:enterprise_linux:6::server | All versions | 0:5.1.66-2.el6_3 | | `mysql` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.1.66-2.el6_3 | | `mysql-bench` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.1.66-2.el6_3 | | `mysql-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.1.66-2.el6_3 | | `mysql-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.1.66-2.el6_3 | | `mysql-embedded` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.1.66-2.el6_3 | | `mysql-embedded-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.1.66-2.el6_3 | | `mysql-libs` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.1.66-2.el6_3 | | `mysql-server` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.1.66-2.el6_3 | | `mysql-test` | Red Hat:enterprise_linux:6::workstation | All versions | 0:5.1.66-2.el6_3 | Products: Mariadb Mariadb, Oracle Mysql. ## How do I fix CVE-2012-5611? Upgrade to a fixed version. ## Is CVE-2012-5611 being exploited? There is no known exploitation of CVE-2012-5611 in the wild and no public exploit code. Public exploit code: - MySQL (Linux) - Stack Buffer Overrun (PoC) (exploitdb) ## Other vulnerabilities in Mariadb Mariadb - [CVE-2026-49261](https://insights.sbomify.com/CVE-2026-49261/): MariaDB server has unsafe parameter handling in `wsrep_notify_cmd` (critical 10.0) - [CVE-2026-85746](https://insights.sbomify.com/CVE-2026-85746/): MariaDB: Out-of-bound buffer write on in `ST_AsText` of nested GeometryCollections (critical 9.9) - [CVE-2026-85748](https://insights.sbomify.com/CVE-2026-85748/): MariaDB: Use-after-free with a large number of SYS_REFCURSOR's (critical 9.9) - [CVE-2026-92262](https://insights.sbomify.com/CVE-2026-92262/): MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass. (critical 9.9) - [CVE-2023-26785](https://insights.sbomify.com/CVE-2023-26785/): Code injection in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2012-5611 and fix it if it is affected. What it is: CVE-2012-5611 is a medium-severity memory corruption vulnerability in Mariadb Mariadb, published on 3 Dec 2012. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2012-5611 in the wild and no public exploit code. Affected product: Mariadb Mariadb. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2012-5611/ (Markdown: https://insights.sbomify.com/CVE-2012-5611/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2012-5611 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-5611 - OSV: https://osv.dev/vulnerability/CVE-2012-5611 --- From sbomify Insights: https://insights.sbomify.com/CVE-2012-5611/ Summaries are generated and may contain mistakes; the official description above is the record.