# CVE-2009-2446: Other in n/a

> Authenticated users can crash the MySQL daemon or potentially execute code via format string vulnerabilities in database creation or deletion commands.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **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:** 13 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1877-1, GHSA-q8wr-mc75-9wjp

## What is CVE-2009-2446?

CVE-2009-2446 is a high-severity vulnerability in Mysql Mysql, published on 13 Jul 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple format string vulnerabilities in the dispatch_command function in libmysqld/sql_parse.cc in mysqld in MySQL 4.0.0 through 5.0.83 allow remote authenticated users to cause a denial of service (daemon crash) and possibly have unspecified other impact via format string specifiers in a database name in a (1) COM_CREATE_DB or (2) COM_DROP_DB request.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2009-2446?

It affects 2 products.


Products: Mysql Mysql, Oracle Mysql.

## How do I fix CVE-2009-2446?

Upgrade to a fixed version.

## Is CVE-2009-2446 being exploited?

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

Public exploit code:

- MySQL 5.0.75 - 'sql_parse.cc' Multiple Format String Vulnerabilities (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-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)
- [CVE-2012-0882](https://insights.sbomify.com/CVE-2012-0882/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2446 and fix it if it is affected.

What it is: CVE-2009-2446 is a high-severity vulnerability in Mysql Mysql, published on 13 Jul 2009. 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-2009-2446 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-2009-2446/ (Markdown: https://insights.sbomify.com/CVE-2009-2446/index.md)
```

## Sources

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

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