# CVE-2006-3215: Security feature bypass in n/a

> Remote attackers can bypass spam and text analysis filters in Clearswift MAILsweeper by sending emails with unrecognized character sets.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** No
- **Published:** 24 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-995f-r3r5-px8v

## What is CVE-2006-3215?

CVE-2006-3215 is a high-severity vulnerability in n/a, published on 24 Jun 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Clearswift MAILsweeper for SMTP before 4.3.20 and MAILsweeper for Exchange before 4.3.20 allows remote attackers to bypass the "text analysis", possibly bypassing SPAM and other filters, by sending an e-mail specifying a non-existent or unrecognized character set.

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

It affects 2 products.


Products: Clearswift Mailsweeper for Exchange, Clearswift Mailsweeper for Smtp.

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

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

## Is CVE-2006-3215 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3216](https://insights.sbomify.com/CVE-2006-3216/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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