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

> Remote attackers can execute arbitrary local files via directory traversal in phpLDAPadmin, potentially leading to code execution or data disclosure.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-4427, DSA-1965-1, GHSA-5jx8-6jmm-pj5j

## What is CVE-2009-4427?

CVE-2009-4427 is a high-severity path traversal vulnerability in n/a, published on 28 Dec 2009. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in cmd.php in phpLDAPadmin 1.1.0.5 allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the cmd parameter.

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

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

It affects 1 product.


Products: Phpldapadmin Project Phpldapadmin.

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

Upgrade to a fixed version.

## Is CVE-2009-4427 being exploited?

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

Public exploit code:

- phpLDAPadmin - Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-12689](https://insights.sbomify.com/CVE-2018-12689/): Other in n/a (critical 9.8)
- [CVE-2011-4075](https://insights.sbomify.com/CVE-2011-4075/): Code injection in n/a (high 7.5)
- [CVE-2005-2793](https://insights.sbomify.com/CVE-2005-2793/): Code injection in n/a (high 7.5)
- [CVE-2005-2654](https://insights.sbomify.com/CVE-2005-2654/): Auth bypass in n/a (high 7.5)
- [CVE-2005-2792](https://insights.sbomify.com/CVE-2005-2792/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4427 and fix it if it is affected.

What it is: CVE-2009-4427 is a high-severity path traversal vulnerability in n/a, published on 28 Dec 2009. It can be exploited 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-2009-4427 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-2009-4427/ (Markdown: https://insights.sbomify.com/CVE-2009-4427/index.md)
```

## Sources

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

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