# CVE-2006-2916: Privilege escalation in n/a

> Local users can gain root privileges because artswrapper fails to verify the setuid call, preventing privilege dropping.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 15 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4532-mwp5-jccg

## What is CVE-2006-2916?

CVE-2006-2916 is a high-severity vulnerability in n/a, published on 15 Jun 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

artswrapper in aRts, when running setuid root on Linux 2.6.0 or later versions, does not check the return value of the setuid function call, which allows local users to gain root privileges by causing setuid to fail, which prevents artsd from dropping privileges.

Weakness: CWE-273 (Improper Check for Dropped Privileges)

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

It affects 1 product.


Products: Kde Arts.

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

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

## Is CVE-2006-2916 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2916 is a high-severity vulnerability in n/a, published on 15 Jun 2006. 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-2006-2916 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-2006-2916/ (Markdown: https://insights.sbomify.com/CVE-2006-2916/index.md)
```

## Sources

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

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