# CVE-2005-2335: Memory corruption in n/a

> Remote attackers can trigger a buffer overflow in Fetchmail via malicious POP3 server responses, potentially executing arbitrary code or causing denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2335, DSA-774-1, GHSA-64xp-j337-hw4c, RHSA-2005:640

## What is CVE-2005-2335?

CVE-2005-2335 is a medium-severity memory corruption vulnerability in n/a, published on 27 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the POP3 client in Fetchmail before 6.2.5.2 allows remote POP3 servers to cause a denial of service and possibly execute arbitrary code via long UIDL responses.  NOTE: a typo in an advisory accidentally used the wrong CVE identifier for the Fetchmail issue. This is the correct identifier.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2005-2335?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fetchmail` | Red Hat:enterprise_linux:3::as | All versions | 0:6.2.0-3.el3.2 |
| `fetchmail-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:6.2.0-3.el3.2 |
| `fetchmail` | Red Hat:enterprise_linux:3::desktop | All versions | 0:6.2.0-3.el3.2 |
| `fetchmail-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:6.2.0-3.el3.2 |
| `fetchmail` | Red Hat:enterprise_linux:3::es | All versions | 0:6.2.0-3.el3.2 |
| `fetchmail-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:6.2.0-3.el3.2 |
| `fetchmail` | Red Hat:enterprise_linux:3::ws | All versions | 0:6.2.0-3.el3.2 |
| `fetchmail-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:6.2.0-3.el3.2 |
| `fetchmail` | Red Hat:enterprise_linux:4::as | All versions | 0:6.2.5-6.el4.2 |
| `fetchmail-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:6.2.5-6.el4.2 |
| `fetchmail` | Red Hat:enterprise_linux:4::desktop | All versions | 0:6.2.5-6.el4.2 |
| `fetchmail-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:6.2.5-6.el4.2 |
| `fetchmail` | Red Hat:enterprise_linux:4::es | All versions | 0:6.2.5-6.el4.2 |
| `fetchmail-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:6.2.5-6.el4.2 |
| `fetchmail` | Red Hat:enterprise_linux:4::ws | All versions | 0:6.2.5-6.el4.2 |
| `fetchmail-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:6.2.5-6.el4.2 |

Products: Fetchmail Fetchmail.

## How do I fix CVE-2005-2335?

Upgrade to a fixed version.

## Is CVE-2005-2335 being exploited?

There is no known exploitation of CVE-2005-2335 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-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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2335 and fix it if it is affected.

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

## Sources

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

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