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

> Authenticated users can execute arbitrary code via a buffer overflow in the qpopper POP3 server's message handling.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-259, GHSA-frx8-9fr9-73ww

## What is CVE-2003-0143?

CVE-2003-0143 is a critical memory corruption vulnerability in n/a, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The pop_msg function in qpopper 4.0.x before 4.0.5fc2 does not null terminate a message buffer after a call to Qvsnprintf, which could allow authenticated users to execute arbitrary code via a buffer overflow in a mdef command with a long macro name.

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

It affects 1 product.


Products: Qualcomm Qpopper.

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

Upgrade to a fixed version.

## Is CVE-2003-0143 being exploited?

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

Public exploit code:

- Qpopper 4.0.x - Remote Memory Corruption (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-1046](https://insights.sbomify.com/CVE-2001-1046/): Memory corruption in n/a (critical 10.0)
- [CVE-1999-0822](https://insights.sbomify.com/CVE-1999-0822/): Memory corruption in n/a (critical 10.0)
- [CVE-1999-0006](https://insights.sbomify.com/CVE-1999-0006/): Memory corruption in n/a (critical 9.8)
- [CVE-2000-0442](https://insights.sbomify.com/CVE-2000-0442/): Privilege escalation in n/a (high 7.5)
- [CVE-2000-0096](https://insights.sbomify.com/CVE-2000-0096/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0143 is a critical memory corruption vulnerability in n/a, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0143 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-0143/ (Markdown: https://insights.sbomify.com/CVE-2003-0143/index.md)
```

## Sources

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

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