# CVE-2004-0666: Memory corruption in n/a

> Remote attackers can crash the application via a buffer overflow in the POP3 client, causing denial of service.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-5p78-xr8q-m3rj

## What is CVE-2004-0666?

CVE-2004-0666 is a high-severity memory corruption vulnerability in n/a, published on 13 Jul 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Off-by-one error in the POP3_readmsg function in popclient 3.0b6 allows remote attackers to cause a denial of service (application crash) via an e-mail message with a certain line length, which leads to a buffer overflow.

## Which versions are affected by CVE-2004-0666?

It affects 1 product.


Products: Popclient Popclient.

## How do I fix CVE-2004-0666?

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

## Is CVE-2004-0666 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0666 and fix it if it is affected.

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

## Sources

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

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