# CVE-2009-0122: Privilege escalation in n/a

> Local attackers can escalate privileges by manipulating file ownership before an administrator installs or upgrades HPLIP on Ubuntu systems.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wxrh-23mc-r3rq

## What is CVE-2009-0122?

CVE-2009-0122 is a medium-severity vulnerability in n/a, published on 15 Jan 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

hplip.postinst in HP Linux Imaging and Printing (HPLIP) 2.7.7 and 2.8.2 on Ubuntu allows local users to change the ownership of arbitrary files via unspecified manipulations in advance of an HPLIP installation or upgrade by an administrator, related to the product's attempt to correct the ownership of its configuration files within home directories.

Weakness: CWE-264

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

It affects 1 product.


Products: Hp Hplip.

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

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

## Is CVE-2009-0122 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0122 is a medium-severity vulnerability in n/a, published on 15 Jan 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-0122 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-2009-0122/ (Markdown: https://insights.sbomify.com/CVE-2009-0122/index.md)
```

## Sources

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

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