# CVE-2009-4030: Path traversal in n/a

> Local attackers can bypass privilege checks via symlink manipulation in MyISAM table creation, potentially accessing unauthorized data or escalating privileges.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Nov 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q8q6-rcmj-g45q

## What is CVE-2009-4030?

CVE-2009-4030 is a medium-severity path traversal vulnerability in Mysql Mysql, published on 30 Nov 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MySQL 5.1.x before 5.1.41 allows local users to bypass certain privilege checks by calling CREATE TABLE on a MyISAM table with modified (1) DATA DIRECTORY or (2) INDEX DIRECTORY arguments that are originally associated with pathnames without symlinks, and that can point to tables created at a future time at which a pathname is modified to contain a symlink to a subdirectory of the MySQL data home directory, related to incorrect calculation of the mysql_unpacked_real_data_home value.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2008-4098 and CVE-2008-2079.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 2 products.


Products: Mysql Mysql, Oracle Mysql.

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

Upgrade to a fixed version.

## Is CVE-2009-4030 being exploited?

There is no known exploitation of CVE-2009-4030 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-2009-4030 and fix it if it is affected.

What it is: CVE-2009-4030 is a medium-severity path traversal vulnerability in Mysql Mysql, published on 30 Nov 2009. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-4030 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-2009-4030/ (Markdown: https://insights.sbomify.com/CVE-2009-4030/index.md)
```

## Sources

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

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