# CVE-2006-5867: Weak cryptography in n/a

> Remote attackers can intercept cleartext passwords via man-in-the-middle attacks due to improper TLS enforcement in fetchmail.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-5867, DSA-1259-1, GHSA-cq85-qr6h-4x5p

## What is CVE-2006-5867?

CVE-2006-5867 is a high-severity vulnerability in n/a, published on 9 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

fetchmail before 6.3.6-rc4 does not properly enforce TLS and may transmit cleartext passwords over unsecured links if certain circumstances occur, which allows remote attackers to obtain sensitive information via man-in-the-middle (MITM) attacks.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Fetchmail Fetchmail.

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

Upgrade to a fixed version.

## Is CVE-2006-5867 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1009](https://insights.sbomify.com/CVE-2001-1009/): Integer overflow in n/a (critical 10.0)
- [CVE-2001-0101](https://insights.sbomify.com/CVE-2001-0101/): Other in n/a (critical 10.0)
- [CVE-2006-5974](https://insights.sbomify.com/CVE-2006-5974/): Null dereference in n/a (high 7.8)
- [CVE-2005-4348](https://insights.sbomify.com/CVE-2005-4348/): Denial of service in n/a (high 7.8)
- [CVE-2002-1365](https://insights.sbomify.com/CVE-2002-1365/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5867 is a high-severity vulnerability in n/a, published on 9 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-5867 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-5867/ (Markdown: https://insights.sbomify.com/CVE-2006-5867/index.md)
```

## Sources

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

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