# CVE-2005-2661: Code injection in n/a

> Remote IMAP servers can execute arbitrary code on up-imapproxy via format string vulnerabilities in banner or capability lines.

- **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:** Yes
- **Published:** 14 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2661, DSA-852-1, GHSA-9jj5-f9v3-4q8v

## What is CVE-2005-2661?

CVE-2005-2661 is a high-severity code injection vulnerability in n/a, published on 14 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Format string vulnerability in the ParseBannerAndCapability function in main.c for up-imapproxy 1.2.3 and 1.2.4 allows remote IMAP servers to execute arbitrary code via format string specifiers in a banner or capability line.

## Which versions are affected by CVE-2005-2661?

It affects 1 product.


Products: Up-Imapproxy Up-Imapproxy.

## How do I fix CVE-2005-2661?

Apply the vendor's patch.

## Is CVE-2005-2661 being exploited?

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

Public exploit code:

- Up-IMAPProxy 1.2.3/1.2.4 - Multiple Unspecified Remote Format String Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2661 and fix it if it is affected.

What it is: CVE-2005-2661 is a high-severity code injection vulnerability in n/a, published on 14 Oct 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-2005-2661 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-2005-2661/ (Markdown: https://insights.sbomify.com/CVE-2005-2661/index.md)
```

## Sources

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

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