# CVE-2004-2703: Security feature bypass in n/a

> Remote attackers can bypass email scanning by sending encrypted messages, which are incorrectly marked as clean in upgraded Clearswift MIMEsweeper installations.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2jm4-cm7h-hghg

## What is CVE-2004-2703?

CVE-2004-2703 is a medium-severity vulnerability in n/a, published on 6 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Clearswift MIMEsweeper 5.0.5, when it has been upgraded from MAILsweeper for SMTP version 4.3 or MAILsweeper Business Suite I or II, allows remote attackers to bypass scanning by including encrypted data in a mail message, which causes the message to be marked as "Clean" instead of "Encrypted".

Weakness: CWE-310

## Which versions are affected by CVE-2004-2703?

It affects 4 products.


Products: Clearswift Mailsweeper Business Suite I, Clearswift Mailsweeper Business Suite Ii, Clearswift Mailsweeper for Smtp, Clearswift Mimesweeper for Web.

## How do I fix CVE-2004-2703?

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

## Is CVE-2004-2703 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2703 and fix it if it is affected.

What it is: CVE-2004-2703 is a medium-severity vulnerability in n/a, published on 6 Oct 2007. 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-2004-2703 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-2004-2703/ (Markdown: https://insights.sbomify.com/CVE-2004-2703/index.md)
```

## Sources

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

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