# CVE-2006-3552: Misconfiguration in n/a

> Attackers can exploit outdated spam filter data to use the server for spam transmission due to improper signature updates.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/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:** 13 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rx2h-jrq8-8mj2

## What is CVE-2006-3552?

CVE-2006-3552 is a medium-severity vulnerability in n/a, published on 13 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Premium Anti-Spam in Ipswitch IMail Secure Server 2006 and Collaboration Suite 2006 Premium, when using a certain .dat file in the StarEngine /data directory from 20060630 or earlier, does not properly receive and implement bullet signature updates, which allows context-dependent attackers to use the server for spam transmission.

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

It affects 2 products.


Products: Ipswitch Ipswitch Collaboration Suite, Ipswitch Ipswitch Secure Server.

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

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

## Is CVE-2006-3552 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0707](https://insights.sbomify.com/CVE-2005-0707/): Memory corruption in n/a (high 7.2)
- [CVE-2005-3526](https://insights.sbomify.com/CVE-2005-3526/): Memory corruption in n/a (medium 6.5)
- [CVE-2005-1249](https://insights.sbomify.com/CVE-2005-1249/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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