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

> Authenticated users can inject arbitrary SMTP commands via the message parameter, potentially bypassing server restrictions and executing code.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qgqm-rhx5-mcpm

## What is CVE-2006-5313?

CVE-2006-5313 is a medium-severity command injection vulnerability in n/a, published on 17 Oct 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hastymail 1.5 and earlier before 20061008 allows remote authenticated users to send arbitrary SMTP commands by placing them after a CRLF.CRLF sequence in the smtp_message parameter.  NOTE: this crosses privilege boundaries if the SMTP server configuration prevents a user from establishing a direct SMTP session.  NOTE: this is a different type of issue than CVE-2006-5262.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Hastymail Hastymail.

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

No fix has been published for CVE-2006-5313 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-5313 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5262](https://insights.sbomify.com/CVE-2006-5262/): Command injection in n/a (medium 6.5)
- [CVE-2004-2704](https://insights.sbomify.com/CVE-2004-2704/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5313 is a medium-severity command injection vulnerability in n/a, published on 17 Oct 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-5313 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-2006-5313/ (Markdown: https://insights.sbomify.com/CVE-2006-5313/index.md)
```

## Sources

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

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