# CVE-2007-2683: Memory corruption in n/a

> Local attackers can execute arbitrary code via buffer overflow in Mutt during alias expansion triggered by GECOS field characters.

- **Severity:** Low 3.5 (`AV:L/AC:H/Au:S/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2683, GHSA-c6h8-qr22-65qm

## What is CVE-2007-2683?

CVE-2007-2683 is a low-severity memory corruption vulnerability in n/a, published on 15 May 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in Mutt 1.4.2 might allow local users to execute arbitrary code via "&" characters in the GECOS field, which triggers the overflow during alias expansion.

## Which versions are affected by CVE-2007-2683?

It affects 1 product.


Products: Mutt Mutt.

## How do I fix CVE-2007-2683?

Upgrade to a fixed version.

## Is CVE-2007-2683 being exploited?

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

Public exploit code:

- Mutt 1.4.2 - Mutt_Gecos_Name Function Local Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-32055](https://insights.sbomify.com/CVE-2021-32055/): Memory corruption in n/a (critical 9.1)
- [CVE-2006-3242](https://insights.sbomify.com/CVE-2006-3242/): Memory corruption in n/a (high 7.5)
- [CVE-2005-2642](https://insights.sbomify.com/CVE-2005-2642/): Memory corruption in n/a (high 7.5)
- [CVE-2004-0078](https://insights.sbomify.com/CVE-2004-0078/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0299](https://insights.sbomify.com/CVE-2003-0299/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2683 and fix it if it is affected.

What it is: CVE-2007-2683 is a low-severity memory corruption vulnerability in n/a, published on 15 May 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2683 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-2007-2683/ (Markdown: https://insights.sbomify.com/CVE-2007-2683/index.md)
```

## Sources

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

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