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

> Remote attackers can execute arbitrary local files via directory traversal in the Horde Image driver, affecting Horde Groupware users.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j5w4-f7qm-4ww8

## What is CVE-2009-0932?

CVE-2009-0932 is a medium-severity path traversal vulnerability in n/a, published on 17 Mar 2009. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in framework/Image/Image.php in Horde before 3.2.4 and 3.3.3 and Horde Groupware before 1.1.5 allows remote attackers to include and execute arbitrary local files via directory traversal sequences in the Horde_Image driver name.

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

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

It affects 2 products.


Products: Debian Horde, Debian Horde Groupware.

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

Upgrade to a fixed version.

## Is CVE-2009-0932 being exploited?

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

Public exploit code:

- Horde - Horde_Image::factory driver Argument Local File Inclusion (exploitdb)
- Horde/Horde Groupware - Local File Inclusion (nuclei): http/cves/2009/CVE-2009-0932.yaml

## Other vulnerabilities in n/a

- [CVE-2009-0931](https://insights.sbomify.com/CVE-2009-0931/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2008-3330](https://insights.sbomify.com/CVE-2008-3330/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0932 is a medium-severity path traversal vulnerability in n/a, published on 17 Mar 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-0932 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-0932/ (Markdown: https://insights.sbomify.com/CVE-2009-0932/index.md)
```

## Sources

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

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