# CVE-2006-4227: Privilege escalation in n/a

> Remote authenticated users can gain privileges by exploiting how MySQL evaluates arguments in stored routines, allowing execution in the definer's security context.

- **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:** 18 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pq6p-m3qv-7m6j

## What is CVE-2006-4227?

CVE-2006-4227 is a medium-severity vulnerability in Mysql Mysql, published on 18 Aug 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MySQL before 5.0.25 and 5.1 before 5.1.12 evaluates arguments of suid routines in the security context of the routine's definer instead of the routine's caller, which allows remote authenticated users to gain privileges through a routine that has been made available using GRANT EXECUTE.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2006-4227?

It affects 2 products.


Products: Mysql Mysql, Oracle Mysql.

## How do I fix CVE-2006-4227?

Upgrade to a fixed version.

## Is CVE-2006-4227 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4227 exists.

Public exploit code:

- MySQL 4/5 - SUID Routine Miscalculation Arbitrary DML Statement Execution (exploitdb)

## Other vulnerabilities in Mysql Mysql

- [CVE-2004-0627](https://insights.sbomify.com/CVE-2004-0627/): Auth bypass in n/a (critical 10.0)
- [CVE-2004-0628](https://insights.sbomify.com/CVE-2004-0628/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-2446](https://insights.sbomify.com/CVE-2009-2446/): Other in n/a (high 8.5)
- [CVE-2012-0553](https://insights.sbomify.com/CVE-2012-0553/): Memory corruption in n/a (high 7.5)
- [CVE-2013-1492](https://insights.sbomify.com/CVE-2013-1492/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4227 and fix it if it is affected.

What it is: CVE-2006-4227 is a medium-severity vulnerability in Mysql Mysql, published on 18 Aug 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4227 exists.

Affected product: Mysql Mysql. 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-2006-4227/ (Markdown: https://insights.sbomify.com/CVE-2006-4227/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-4227
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-4227
- OSV: https://osv.dev/vulnerability/CVE-2006-4227

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-4227/
Summaries are generated and may contain mistakes; the official description above is the record.