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

> Remote authenticated users can gain privileges in Linux Netkit ftpd if system calls fail due to unchecked return values.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Nov 2006
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2006-6008, GHSA-hwph-788h-xp87

## What is CVE-2006-6008?

CVE-2006-6008 is a medium-severity vulnerability in n/a, published on 21 Nov 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ftpd in Linux Netkit (linux-ftpd) 0.17, and possibly other versions, does not check the return status of certain seteuid, setgid, and setuid calls, which might allow remote authenticated users to gain privileges if these calls fail in cases such as PAM failures or resource limits, a different vulnerability than CVE-2006-5778.

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

It affects 1 product.


Products: Netkit Netkit.

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

Apply the vendor's patch.

## Is CVE-2006-6008 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-38336](https://insights.sbomify.com/CVE-2023-38336/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6008 is a medium-severity vulnerability in n/a, published on 21 Nov 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-6008 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-6008/ (Markdown: https://insights.sbomify.com/CVE-2006-6008/index.md)
```

## Sources

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

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