# CVE-2007-5970: Privilege escalation in n/a

> Authenticated users can escalate privileges on arbitrary tables by exploiting partitioned table creation with directory options.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **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:** 10 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4pw7-3p8h-fr77

## What is CVE-2007-5970?

CVE-2007-5970 is a medium-severity vulnerability in Oracle Mysql, published on 10 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MySQL 5.1.x before 5.1.23 and 6.0.x before 6.0.4 allows remote authenticated users to gain privileges on arbitrary tables via unspecified vectors involving use of table-level DATA DIRECTORY and INDEX DIRECTORY options when creating a partitioned table with the same name as a table on which the user lacks privileges.

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

It affects 1 product.


Products: Oracle Mysql.

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

Upgrade to a fixed version.

## Is CVE-2007-5970 being exploited?

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

## Other vulnerabilities in Oracle Mysql

- [CVE-2016-0639](https://insights.sbomify.com/CVE-2016-0639/): Auth bypass in n/a (critical 9.8)
- [CVE-2003-0150](https://insights.sbomify.com/CVE-2003-0150/): Privilege escalation in n/a (critical 9.0)
- [CVE-2005-2572](https://insights.sbomify.com/CVE-2005-2572/): Denial of service in n/a (high 8.5)
- [CVE-2020-14878](https://insights.sbomify.com/CVE-2020-14878/): Auth bypass in MySQL Server (high 8.0)
- [CVE-2002-0969](https://insights.sbomify.com/CVE-2002-0969/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5970 and fix it if it is affected.

What it is: CVE-2007-5970 is a medium-severity vulnerability in Oracle Mysql, published on 10 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-5970 in the wild and no public exploit code.

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

## Sources

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

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