# CVE-2008-0162: Privilege escalation in n/a

> Local attackers can gain elevated privileges because splitvt fails to drop group permissions before executing xprop.

- **Severity:** High 7.2 (`AV:L/AC:L/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:** Not needed
- **Fix available:** Yes
- **Published:** 22 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-0162, DSA-1500-1, GHSA-42fh-f837-4fj4

## What is CVE-2008-0162?

CVE-2008-0162 is a high-severity vulnerability in n/a, published on 22 Feb 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

misc.c in splitvt 1.6.6 and earlier does not drop group privileges before executing xprop, which allows local users to gain privileges.

Weakness: CWE-264

## Which versions are affected by CVE-2008-0162?

It affects 1 product.


Products: Sam Lantinga Splitvt.

## How do I fix CVE-2008-0162?

Apply the vendor's patch.

## Is CVE-2008-0162 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-0467](https://insights.sbomify.com/CVE-2000-0467/): Memory corruption in n/a (high 7.2)
- [CVE-1999-0316](https://insights.sbomify.com/CVE-1999-0316/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0162 and fix it if it is affected.

What it is: CVE-2008-0162 is a high-severity vulnerability in n/a, published on 22 Feb 2008. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-0162 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-2008-0162/ (Markdown: https://insights.sbomify.com/CVE-2008-0162/index.md)
```

## Sources

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

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