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

> Local attackers can modify insecure package permissions to gain root privileges on client systems via Apple Remote Desktop administration.

- **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:** No
- **Published:** 18 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q78v-f3vf-m3qq

## What is CVE-2006-4413?

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

### Official description

Apple Remote Desktop before 3.1 uses insecure permissions for certain built-in packages, which allows local users on an Apple Remote Desktop administration system to modify the packages and gain root privileges on client systems that use the packages.

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

It affects 1 product.


Products: Apple Remote Desktop.

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

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

## Is CVE-2006-4413 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-2488](https://insights.sbomify.com/CVE-2017-2488/): Weak cryptography in Apple Remote Desktop (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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