# CVE-2006-6680: Information disclosure in n/a

> Local attackers can read sensitive configuration data from chetcpasswd.allow due to missing documentation on required file permissions.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Dec 2006
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8v6h-p83g-qp55

## What is CVE-2006-6680?

CVE-2006-6680 is a medium-severity vulnerability in n/a, published on 21 Dec 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Pedro Lineu Orso chetcpasswd before 2.3.1 does not document the need for 0400 permissions on /etc/chetcpasswd.allow, which might allow local users to gain sensitive information by reading this file.

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

It affects 1 product.


Products: Chetcpasswd Chetcpasswd.

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

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

## Is CVE-2006-6680 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2219](https://insights.sbomify.com/CVE-2002-2219/): Information disclosure in n/a (high 7.5)
- [CVE-2006-6681](https://insights.sbomify.com/CVE-2006-6681/): Denial of service in n/a (high 7.5)
- [CVE-2002-2220](https://insights.sbomify.com/CVE-2002-2220/): Memory corruption in n/a (medium 6.2)
- [CVE-2002-2221](https://insights.sbomify.com/CVE-2002-2221/): Privilege escalation in n/a (medium 6.2)
- [CVE-2006-6639](https://insights.sbomify.com/CVE-2006-6639/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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