# CVE-2006-2447: Command injection in n/a

> Remote attackers can execute arbitrary commands on SpamAssassin servers using vpopmail and the paranoid switch via crafted messages.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** 6 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2447, DSA-1090-1, GHSA-xj48-9vrg-vxxc, RHSA-2006:0543

## What is CVE-2006-2447?

CVE-2006-2447 is a medium-severity command injection vulnerability in n/a, published on 6 Jun 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SpamAssassin before 3.1.3, when running with vpopmail and the paranoid (-P) switch, allows remote attackers to execute arbitrary commands via a crafted message that is not properly handled when invoking spamd with the virtual pop username.

## Which versions are affected by CVE-2006-2447?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `spamassassin` | Red Hat:enterprise_linux:4::as | All versions | 0:3.0.6-1.el4 |
| `spamassassin-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:3.0.6-1.el4 |
| `spamassassin` | Red Hat:enterprise_linux:4::desktop | All versions | 0:3.0.6-1.el4 |
| `spamassassin-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:3.0.6-1.el4 |
| `spamassassin` | Red Hat:enterprise_linux:4::es | All versions | 0:3.0.6-1.el4 |
| `spamassassin-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:3.0.6-1.el4 |
| `spamassassin` | Red Hat:enterprise_linux:4::ws | All versions | 0:3.0.6-1.el4 |
| `spamassassin-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:3.0.6-1.el4 |

Products: Apache Spamassassin.

## How do I fix CVE-2006-2447?

Upgrade to a fixed version.

## Is CVE-2006-2447 being exploited?

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

Public exploit code:

- SpamAssassin spamd 3.1.3 - Command Injection (Metasploit) (exploitdb)
- SpamAssassin spamd Remote Command Execution (metasploit)
- SpamAssassin spamd - Remote Command Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-1946](https://insights.sbomify.com/CVE-2020-1946/): Apache SpamAssassin has an OS Command Injection vulnerability (critical 9.8)
- [CVE-2018-11780](https://insights.sbomify.com/CVE-2018-11780/): Code injection in Apache SpamAssassin (critical 9.8)
- [CVE-2020-1930](https://insights.sbomify.com/CVE-2020-1930/): Command injection in Apache SpamAssassin (high 8.1)
- [CVE-2020-1931](https://insights.sbomify.com/CVE-2020-1931/): Command injection in Apache SpamAssassin (high 8.1)
- [CVE-2018-11781](https://insights.sbomify.com/CVE-2018-11781/): Apache SpamAssassin 3.4.2 fixes a local user code injection in the meta rule syntax. (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2447 and fix it if it is affected.

What it is: CVE-2006-2447 is a medium-severity command injection vulnerability in n/a, published on 6 Jun 2006. 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-2006-2447 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-2006-2447/ (Markdown: https://insights.sbomify.com/CVE-2006-2447/index.md)
```

## Sources

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

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