# CVE-2004-2439: Missing authorization in n/a

> Remote attackers can upgrade firmware on HP LaserJet printers without authentication, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 20 Aug 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2gf9-crwq-fg52

## What is CVE-2004-2439?

CVE-2004-2439 is a medium-severity missing authorization vulnerability in n/a, published on 20 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The remote upgrade capability in HP LaserJet 4200 and 4300 printers does not require a password, which allows remote attackers to upgrade firmware.

## Which versions are affected by CVE-2004-2439?

It affects 17 products.


Products: Hp Color Laserjet, Hp Color Laserjet 4600, Hp Laserjet 2500, Hp Laserjet 3000, Hp Laserjet 3700, Hp Laserjet 4100 Mfp, Hp Laserjet 4200, Hp Laserjet 4300, Hp Laserjet 9000, Hp Laserjet 9000 Mfp, Hp Laserjet 9040 Mpf, Hp Laserjet 9050, Hp Laserjet 9050 Mpf, Hp Laserjet 9055, Hp Laserjet 9065, Hp Laserjet 9500, Hp Laserjet 9500 Mpf.

## How do I fix CVE-2004-2439?

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

## Is CVE-2004-2439 being exploited?

There is no known exploitation of CVE-2004-2439 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2006-1654](https://insights.sbomify.com/CVE-2006-1654/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2439 and fix it if it is affected.

What it is: CVE-2004-2439 is a medium-severity missing authorization vulnerability in n/a, published on 20 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-2439 in the wild and no public exploit code.

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-2004-2439/ (Markdown: https://insights.sbomify.com/CVE-2004-2439/index.md)
```

## Sources

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

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