# CVE-2007-6304: Denial of service in n/a

> Remote MySQL servers can crash the federated handler and daemon via malformed responses to SHOW TABLE STATUS queries, causing denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2008-0627, GHSA-gmq9-53hm-68cj

## What is CVE-2007-6304?

CVE-2007-6304 is a medium-severity denial of service vulnerability in Mysql Mysql, published on 10 Dec 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The federated engine in MySQL 5.0.x before 5.0.51a, 5.1.x before 5.1.23, and 6.0.x before 6.0.4, when performing a certain SHOW TABLE STATUS query, allows remote MySQL servers to cause a denial of service (federated handler crash and daemon crash) via a response that lacks the minimum required number of columns.

## Which versions are affected by CVE-2007-6304?

It affects 2 products.


Products: Mysql Mysql, Oracle Mysql.

## How do I fix CVE-2007-6304?

Upgrade to a fixed version.

## Is CVE-2007-6304 being exploited?

There is no known exploitation of CVE-2007-6304 in the wild and no public exploit code.

## 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-2007-6304 and fix it if it is affected.

What it is: CVE-2007-6304 is a medium-severity denial of service vulnerability in Mysql Mysql, published on 10 Dec 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-6304 in the wild and no public exploit code.

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-2007-6304/ (Markdown: https://insights.sbomify.com/CVE-2007-6304/index.md)
```

## Sources

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

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