# CVE-2006-5974: Null dereference in n/a

> Remote attackers can crash fetchmail via a NULL pointer dereference when the mda option is configured to refuse messages.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **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-5974, GHSA-qjgr-cmw7-hw63

## What is CVE-2006-5974?

CVE-2006-5974 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 6.3.5 and 6.3.6 before 6.3.6-rc4, when refusing a message delivered via the mda option, allows remote attackers to cause a denial of service (crash) via unknown vectors that trigger a NULL pointer dereference when calling the (1) ferror or (2) fflush functions.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Fetchmail Fetchmail.

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

Upgrade to a fixed version.

## Is CVE-2006-5974 being exploited?

There is no known exploitation of CVE-2006-5974 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-5867](https://insights.sbomify.com/CVE-2006-5867/): Weak cryptography 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-5974 and fix it if it is affected.

What it is: CVE-2006-5974 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-5974 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-5974/ (Markdown: https://insights.sbomify.com/CVE-2006-5974/index.md)
```

## Sources

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

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