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

> Remote attackers can cause denial of service or execute arbitrary code on qmail servers via a malformed SMTP command triggering a negative array index.

- **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:** 11 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-45cm-3mvx-7pjc, UBUNTU-CVE-2005-1514

## What is CVE-2005-1514?

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

### Official description

commands.c in qmail, when running on 64 bit platforms with a large amount of virtual memory, allows remote attackers to cause a denial of service and possibly execute arbitrary code via a long SMTP command without a space character, which causes an array to be referenced with a negative index.

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

It affects 1 product.


Products: Dan Bernstein Qmail.

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

Apply the vendor's patch.

## Is CVE-2005-1514 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-0250](https://insights.sbomify.com/CVE-1999-0250/): Denial of service in n/a (critical 10.0)
- [CVE-2005-1515](https://insights.sbomify.com/CVE-2005-1515/): Integer overflow in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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