# CVE-2008-4454: Path traversal in n/a

> Remote attackers can read and execute arbitrary files via directory traversal in the lang parameter of MySQL Quick Admin.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2008
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-53x8-fc7q-4wwg

## What is CVE-2008-4454?

CVE-2008-4454 is a medium-severity path traversal vulnerability in n/a, published on 6 Oct 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in EKINdesigns MySQL Quick Admin 1.5.5 allows remote attackers to read and execute arbitrary files via a .. (dot dot) in the lang parameter to actions.php.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2008-4454?

It affects 1 product.


Products: Mysql Quick Admin Mysql Quick Admin.

## How do I fix CVE-2008-4454?

No fix has been published for CVE-2008-4454 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-4454 being exploited?

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

Public exploit code:

- MySQL Quick Admin 1.5.5 - 'cookie' Local File Inclusion (exploitdb)
- MySQL Quick Admin 1.5.5 - Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-4455](https://insights.sbomify.com/CVE-2008-4455/): Path traversal in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-4454 and fix it if it is affected.

What it is: CVE-2008-4454 is a medium-severity path traversal vulnerability in n/a, published on 6 Oct 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-4454 exists.

Affected product: n/a. 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-2008-4454/ (Markdown: https://insights.sbomify.com/CVE-2008-4454/index.md)
```

## Sources

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

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