# CVE-2009-2632: Memory corruption in n/a

> Local attackers can execute arbitrary code and access messages via crafted SIEVE scripts due to buffer overflow in Cyrus IMAP and Dovecot.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-2632, DSA-1881-1, GHSA-f78m-3xxg-82w8

## What is CVE-2009-2632?

CVE-2009-2632 is a medium-severity memory corruption vulnerability in n/a, published on 8 Sep 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in the SIEVE script component (sieve/script.c), as used in cyrus-imapd in Cyrus IMAP Server 2.2.13 and 2.3.14, and Dovecot 1.0 before 1.0.4 and 1.1 before 1.1.7, allows local users to execute arbitrary code and read or modify arbitrary messages via a crafted SIEVE script, related to the incorrect use of the sizeof operator for determining buffer length, combined with an integer signedness error.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2009-2632?

It affects 1 product.


Products: Cmu Cyrus Imap Server.

## How do I fix CVE-2009-2632?

Upgrade to a fixed version.

## Is CVE-2009-2632 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-3208](https://insights.sbomify.com/CVE-2011-3208/): Memory corruption in n/a (high 7.5)
- [CVE-2011-1926](https://insights.sbomify.com/CVE-2011-1926/): Other in n/a (medium 5.1)
- [CVE-2011-3481](https://insights.sbomify.com/CVE-2011-3481/): Null dereference in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2632 and fix it if it is affected.

What it is: CVE-2009-2632 is a medium-severity memory corruption vulnerability in n/a, published on 8 Sep 2009. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-2632 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-2009-2632/ (Markdown: https://insights.sbomify.com/CVE-2009-2632/index.md)
```

## Sources

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

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