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

> Remote attackers can read arbitrary files via path traversal in html2ps when invoked by a web application or via user-assisted attacks.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Oct 2012
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-5067, GHSA-q52q-xhwr-p2mr

## What is CVE-2009-5067?

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

### Official description

Directory traversal vulnerability in html2ps before 1.0b6 allows remote attackers to read arbitrary files via a .. (dot dot) in the "include file" SSI directive.  NOTE: this issue only might be a vulnerability in limited scenarios, such as if html2ps is invoked by a web application, or if a user-assisted attacker provides filenames whose contents could cause a denial of service, such as certain devices.

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

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

It affects 1 product.


Products: Html2ps Project Html2ps.

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

Upgrade to a fixed version.

## Is CVE-2009-5067 being exploited?

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

Public exploit code:

- html2ps - 'include file' Server-Side Include Directive Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-1275](https://insights.sbomify.com/CVE-2002-1275/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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