# CVE-2003-0297: Integer overflow in n/a

> Remote malicious IMAP servers can crash the client or execute arbitrary code via integer overflow errors in size values.

- **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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 May 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0297, GHSA-22ph-2jjc-cggf

## What is CVE-2003-0297?

CVE-2003-0297 is a high-severity vulnerability in n/a, published on 15 May 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

c-client IMAP Client, as used in imap-2002b and Pine 4.53, allows remote malicious IMAP servers to cause a denial of service (crash) and possibly execute arbitrary code via certain large (1) literal and (2) mailbox size values that cause either integer signedness errors or integer overflow errors.

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

It affects 3 products.


Products: University of Washington C-Client, University of Washington Imap-2002b, University of Washington Pine.

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

Upgrade to a fixed version.

## Is CVE-2003-0297 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0297 is a high-severity vulnerability in n/a, published on 15 May 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2003-0297 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-0297/ (Markdown: https://insights.sbomify.com/CVE-2003-0297/index.md)
```

## Sources

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

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