# CVE-2003-0057: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via buffer overflows in Hypermail's attachment handling or CGI hostname processing.

- **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:** 1 Feb 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-248, GHSA-p3ch-8ghm-h778

## What is CVE-2003-0057?

CVE-2003-0057 is a high-severity memory corruption vulnerability in n/a, published on 1 Feb 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple buffer overflows in Hypermail 2 before 2.1.6 allows remote attackers to cause a denial of service and possibly execute arbitrary code (1) via a long attachment filename that is not properly handled by the hypermail executable, or (2) by connecting to the mail CGI program from an IP address that reverse-resolves to a long hostname.

## Which versions are affected by CVE-2003-0057?

It affects 1 product.


Products: Hypermail Hypermail.

## How do I fix CVE-2003-0057?

Upgrade to a fixed version.

## Is CVE-2003-0057 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0057 and fix it if it is affected.

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

## Sources

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

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