# CVE-2004-0129: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in phpMyAdmin's export functionality, exposing sensitive system data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0129, GHSA-f766-fjw3-vvfv

## What is CVE-2004-0129?

CVE-2004-0129 is a medium-severity path traversal vulnerability in Phpmyadmin Phpmyadmin, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in export.php in phpMyAdmin 2.5.5 and earlier allows remote attackers to read arbitrary files via .. (dot dot) sequences in the what parameter.

## Which versions are affected by CVE-2004-0129?

It affects 1 product.


Products: Phpmyadmin Phpmyadmin.

## How do I fix CVE-2004-0129?

Upgrade to a fixed version.

## Is CVE-2004-0129 being exploited?

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

Public exploit code:

- phpMyAdmin 2.x - 'Export.php' File Disclosure (exploitdb)

## Other vulnerabilities in Phpmyadmin Phpmyadmin

- [CVE-2008-7251](https://insights.sbomify.com/CVE-2008-7251/): Misconfiguration in n/a (critical 10.0)
- [CVE-2008-7252](https://insights.sbomify.com/CVE-2008-7252/): phpMyAdmin unsafely handles temporary files (critical 10.0)
- [CVE-2007-0203](https://insights.sbomify.com/CVE-2007-0203/): Other in n/a (critical 10.0)
- [CVE-2004-1147](https://insights.sbomify.com/CVE-2004-1147/): Command injection in n/a (critical 10.0)
- [CVE-2020-22452](https://insights.sbomify.com/CVE-2020-22452/): phpmyadmin contains SQL Injection vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0129 and fix it if it is affected.

What it is: CVE-2004-0129 is a medium-severity path traversal vulnerability in Phpmyadmin Phpmyadmin, published on 1 Sep 2004. 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-2004-0129 exists.

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

## Sources

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

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