# CVE-2005-0709: Code injection in n/a

> Authenticated users with specific privileges can execute arbitrary code via CREATE FUNCTION, requiring an upgrade to secure the database.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/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:** 11 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3x8w-p58r-45ff

## What is CVE-2005-0709?

CVE-2005-0709 is a medium-severity code injection vulnerability in Mysql Mysql, published on 11 Mar 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MySQL 4.0.23 and earlier, and 4.1.x up to 4.1.10, allows remote authenticated users with INSERT and DELETE privileges to execute arbitrary code by using CREATE FUNCTION to access libc calls, as demonstrated by using strcat, on_exit, and exit.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2005-0709?

It affects 2 products.


Products: Mysql Mysql, Oracle Mysql.

## How do I fix CVE-2005-0709?

Upgrade to a fixed version.

## Is CVE-2005-0709 being exploited?

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

Public exploit code:

- MySQL 4.x - CREATE FUNCTION Arbitrary libc Code 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-2005-0709 and fix it if it is affected.

What it is: CVE-2005-0709 is a medium-severity code injection vulnerability in Mysql Mysql, published on 11 Mar 2005. 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-2005-0709 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-2005-0709/ (Markdown: https://insights.sbomify.com/CVE-2005-0709/index.md)
```

## Sources

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

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