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

> Remote attackers can crash the Mathopd web server or execute arbitrary code via a buffer overflow in HTTP request handling.

- **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:** 16 Aug 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9c8p-6c5j-w6c4

## What is CVE-2003-1228?

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

### Official description

Buffer overflow in the prepare_reply function in request.c for Mathopd 1.2 through 1.5b13, and possibly earlier versions, allows remote attackers to cause a denial of service (server crash) and possibly execute arbitrary code via an HTTP request with a long path.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Mathopd Mathopd.

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

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

## Is CVE-2003-1228 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1228 exists.

Public exploit code:

- MathoPD 1.x - Remote Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-0824](https://insights.sbomify.com/CVE-2005-0824/): Path traversal in n/a (medium 5.5)
- [CVE-2012-1050](https://insights.sbomify.com/CVE-2012-1050/): Path traversal in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-1228 is a high-severity memory corruption vulnerability in n/a, published on 16 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1228 exists.

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-1228/ (Markdown: https://insights.sbomify.com/CVE-2003-1228/index.md)
```

## Sources

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

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