# CVE-2004-1035: Integer overflow in n/a

> Remote attackers can crash the IMAP proxy or leak sensitive data via integer signedness errors in literal value handling.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 16 Nov 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-1035, GHSA-jfvg-fhfm-45f8

## What is CVE-2004-1035?

CVE-2004-1035 is a medium-severity vulnerability in n/a, published on 16 Nov 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple integer signedness errors in (1) imapcommon.c, (2) main.c, (3) request.c, and (4) select.c for up-imapproxy IMAP proxy 1.2.2 allow remote attackers to cause a denial of service (server crash) and possibly leak sensitive information via certain literal values that are not properly handled when using the IMAP_Line_Read function.

## Which versions are affected by CVE-2004-1035?

It affects 1 product.


Products: Imap Proxy Imap Proxy.

## How do I fix CVE-2004-1035?

Upgrade to a fixed version.

## Is CVE-2004-1035 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1035 and fix it if it is affected.

What it is: CVE-2004-1035 is a medium-severity vulnerability in n/a, published on 16 Nov 2004. 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-2004-1035 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-2004-1035/ (Markdown: https://insights.sbomify.com/CVE-2004-1035/index.md)
```

## Sources

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

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