# CVE-2007-0161: Privilege escalation in n/a

> Local attackers can exploit insecure permissions in the HP PML Driver to modify service configuration and execute arbitrary code with elevated privileges.

- **Severity:** Medium 4.1 (`AV:L/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6phm-q33g-2xxv

## What is CVE-2007-0161?

CVE-2007-0161 is a medium-severity vulnerability in n/a, published on 10 Jan 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The PML Driver HPZ12 (HPZipm12.exe) in the HP all-in-one drivers, as used by multiple HP products, uses insecure SERVICE_CHANGE_CONFIG DACL permissions, which allows local users to gain privileges and execute arbitrary programs, as demonstrated by modifying the binpath argument, a related issue to CVE-2006-0023.

## Which versions are affected by CVE-2007-0161?

It affects 21 products.


Products: Hp Color Laserjet 4650, Hp Officejet 4100, Hp Officejet 5100, Hp Officejet 5500, Hp Officejet 6100, Hp Officejet 7100, Hp Officejet D, Hp Officejet G, Hp Officejet K, Hp Pml Driver Hpz12, Hp Psc 1100, Hp Psc 1200, Hp Psc 1210 All-in-One, Hp Psc 1300, Hp Psc 2100, Hp Psc 2200, Hp Psc 2400 Photosmart All-in-One, Hp Psc 2500 Photosmart All-in-One, Hp Psc 2510 Photosmart, Hp Psc 700 and 1 more.

## How do I fix CVE-2007-0161?

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

## Is CVE-2007-0161 being exploited?

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

Public exploit code:

- HP (Multiple Products) - PML Driver HPZ12 Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0161 and fix it if it is affected.

What it is: CVE-2007-0161 is a medium-severity vulnerability in n/a, published on 10 Jan 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0161 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-2007-0161/ (Markdown: https://insights.sbomify.com/CVE-2007-0161/index.md)
```

## Sources

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

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