# CVE-2010-1132: Command injection in n/a

> Remote attackers can execute arbitrary system commands via shell metacharacters in the RCPT TO field when the expand option is enabled.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-1132, DSA-2021-1, DSA-2021-2, GHSA-mm8j-8fj4-43p5

## What is CVE-2010-1132?

CVE-2010-1132 is a critical command injection vulnerability in n/a, published on 26 Mar 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The mlfi_envrcpt function in spamass-milter.cpp in SpamAssassin Milter Plugin 0.3.1, when using the expand option, allows remote attackers to execute arbitrary system commands via shell metacharacters in the RCPT TO field of an email message.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2010-1132?

It affects 1 product.


Products: Georg Greve Spamassassin Milter Plugin.

## How do I fix CVE-2010-1132?

Apply the vendor's patch.

## Is CVE-2010-1132 being exploited?

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

Public exploit code:

- Apache SpamAssassin Milter Plugin 0.3.1 - Remote Command Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1132 and fix it if it is affected.

What it is: CVE-2010-1132 is a critical command injection vulnerability in n/a, published on 26 Mar 2010. 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-2010-1132 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-2010-1132/ (Markdown: https://insights.sbomify.com/CVE-2010-1132/index.md)
```

## Sources

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

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