# CVE-2002-0379: Memory corruption in n/a

> Remote authenticated users can execute arbitrary code via a buffer overflow in the UW IMAP server when legacy RFC 1730 support is enabled.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cqq9-qgwr-48j4

## What is CVE-2002-0379?

CVE-2002-0379 is a high-severity memory corruption vulnerability in n/a, published on 2 Apr 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in University of Washington imap server (uw-imapd) imap-2001 (imapd 2001.315) and imap-2001a (imapd 2001.315) with legacy RFC 1730 support, and imapd 2000.287 and earlier, allows remote authenticated users to execute arbitrary code via a long BODY request.

## Which versions are affected by CVE-2002-0379?

It affects 1 product.


Products: University of Washington Uw-Imap.

## How do I fix CVE-2002-0379?

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

## Is CVE-2002-0379 being exploited?

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

Public exploit code:

- WU-IMAPd 2000/2001 - Partial Mailbox Attribute Remote Buffer Overflow (1) (exploitdb)
- WU-IMAPd 2000/2001 - Partial Mailbox Attribute Remote Buffer Overflow (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-2933](https://insights.sbomify.com/CVE-2005-2933/): Memory corruption in n/a (high 7.5)
- [CVE-2005-0198](https://insights.sbomify.com/CVE-2005-0198/): Auth bypass in n/a (high 7.5)
- [CVE-2002-1782](https://insights.sbomify.com/CVE-2002-1782/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0379 and fix it if it is affected.

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

## Sources

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

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