# CVE-2006-1654: Path traversal in n/a

> Remote attackers can read arbitrary files on HP Color LaserJet printers via directory traversal in HTTP requests.

- **Severity:** Medium 5.0 (`AV:N/AC:L/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:** No
- **Published:** 6 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5hc7-j537-3jg8

## What is CVE-2006-1654?

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

### Official description

Directory traversal vulnerability in the HP Color LaserJet 2500 Toolbox and Color LaserJet 4600 Toolbox on Microsoft Windows before 20060402 allows remote attackers to read arbitrary files via a .. (dot dot) in an HTTP GET request to TCP port 5225.

## Which versions are affected by CVE-2006-1654?

It affects 9 products.


Products: Hp Color Laserjet, Hp Color Laserjet 2500, Hp Color Laserjet 2500 Toolbox, Hp Color Laserjet 2500l, Hp Color Laserjet 2500lse, Hp Color Laserjet 2500n, Hp Color Laserjet 2500tn, Hp Color Laserjet 4600, Hp Color Laserjet 4600 Toolbox.

## How do I fix CVE-2006-1654?

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

## Is CVE-2006-1654 being exploited?

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

Public exploit code:

- HP Color LaserJet 2500/4600 Toolbox - Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-2439](https://insights.sbomify.com/CVE-2004-2439/): Missing authorization in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1654 and fix it if it is affected.

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

## Sources

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

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