# CVE-2008-2784: Security feature bypass in n/a

> Remote attackers can bypass spam filtering to use the server as an open mail relay by exploiting improper RCPT command handling after DATA commands.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/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:** No
- **Published:** 19 Jun 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-23c2-5fj7-4rv3

## What is CVE-2008-2784?

CVE-2008-2784 is a medium-severity vulnerability in n/a, published on 19 Jun 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The smtp_filter function in spamdyke before 3.1.8 does not filter RCPT commands after encountering the first DATA command, which allows remote attackers to use the server as an open mail relay by sending RCPT commands with invalid recipients, followed by a DATA command, followed by arbitrary RCPT commands and a second DATA command.

Weakness: CWE-264

## Which versions are affected by CVE-2008-2784?

It affects 1 product.


Products: Spamdyke Spamdyke.

## How do I fix CVE-2008-2784?

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

## Is CVE-2008-2784 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0070](https://insights.sbomify.com/CVE-2012-0070/): Information disclosure in spamdyke (high 7.5)
- [CVE-2012-0802](https://insights.sbomify.com/CVE-2012-0802/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2784 and fix it if it is affected.

What it is: CVE-2008-2784 is a medium-severity vulnerability in n/a, published on 19 Jun 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-2784 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-2008-2784/ (Markdown: https://insights.sbomify.com/CVE-2008-2784/index.md)
```

## Sources

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

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