# CVE-2005-1521: Integer overflow in n/a

> Remote attackers can execute arbitrary code on GNU Mailutils IMAP servers via a heap-based buffer overflow triggered by a large END parameter in partial message requests.

- **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:** Yes
- **Published:** 26 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-1521, GHSA-p738-58m7-hr43

## What is CVE-2005-1521?

CVE-2005-1521 is a high-severity vulnerability in n/a, published on 26 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer overflow in the fetch_io function of the imap4d server in GNU Mailutils 0.5 and 0.6, and other versions before 0.6.90, allows remote attackers to execute arbitrary code via a partial message request with a large value in the END parameter, which leads to a heap-based buffer overflow.

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

It affects 1 product.


Products: Gnu Mailutils.

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

Upgrade to a fixed version.

## Is CVE-2005-1521 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-18862](https://insights.sbomify.com/CVE-2019-18862/): Privilege escalation in n/a (high 7.8)
- [CVE-2005-2878](https://insights.sbomify.com/CVE-2005-2878/): Code injection in n/a (high 7.5)
- [CVE-2005-1824](https://insights.sbomify.com/CVE-2005-1824/): SQL injection in n/a (high 7.5)
- [CVE-2005-1520](https://insights.sbomify.com/CVE-2005-1520/): Memory corruption in n/a (high 7.5)
- [CVE-2005-1523](https://insights.sbomify.com/CVE-2005-1523/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1521 is a high-severity vulnerability in n/a, published on 26 May 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-1521 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-1521/ (Markdown: https://insights.sbomify.com/CVE-2005-1521/index.md)
```

## Sources

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

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