# CVE-2006-6683: Auth bypass in n/a

> Attackers can bypass PAM restrictions to update user accounts, potentially escalating privileges or gaining unauthorized access.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Dec 2006
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rqrq-c7rw-wmc4

## What is CVE-2006-6683?

CVE-2006-6683 is a high-severity authentication bypass vulnerability in n/a, published on 21 Dec 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pedro Lineu Orso chetcpasswd 2.4.1 and earlier verifies and updates user accounts via custom code that processes /etc/shadow and does not follow the PAM configuration, which might allow remote attackers to bypass intended restrictions implemented through PAM.

Weakness: CWE-264

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

It affects 1 product.


Products: Pedro Lineu Orso Chetcpasswd.

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

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

## Is CVE-2006-6683 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6684](https://insights.sbomify.com/CVE-2006-6684/): Memory corruption in n/a (high 7.5)
- [CVE-2006-6685](https://insights.sbomify.com/CVE-2006-6685/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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