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

> Local attackers can gain privileges by causing the winbind plugin in pppd to fail dropping privileges due to unchecked setuid return codes.

- **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:** 5 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2194, DSA-1106, GHSA-wh53-gc5h-qjj9

## What is CVE-2006-2194?

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

### Official description

The winbind plugin in pppd for ppp 2.4.4 and earlier does not check the return code from the setuid function call, which might allow local users to gain privileges by causing setuid to fail, such as exceeding PAM limits for the maximum number of user processes, which prevents the winbind NTLM authentication helper from dropping privileges.

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

It affects 1 product.


Products: Point-to-Point Protocol Project Point-to-Point Protocol.

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

Apply the vendor's patch.

## Is CVE-2006-2194 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-3158](https://insights.sbomify.com/CVE-2014-3158/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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