# CVE-2008-7094: Denial of service in n/a

> Remote attackers can crash the Unica Affinium Campaign listener server by sending a crafted length field, causing denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 26 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-236w-f35g-f339

## What is CVE-2008-7094?

CVE-2008-7094 is a medium-severity denial of service vulnerability in n/a, published on 26 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Campaign/CampaignListener in the listener server in Unica Affinium Campaign 7.2.1.0.55 allows remote attackers to cause a denial of service (server crash) via a crafted length field that triggers (1) connection exhaustion or (2) memory allocation failure.

Weakness: CWE-399

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

It affects 1 product.


Products: Unica Affinium Campaign.

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

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

## Is CVE-2008-7094 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-7093](https://insights.sbomify.com/CVE-2008-7093/): Path traversal in n/a (medium 6.8)
- [CVE-2008-7092](https://insights.sbomify.com/CVE-2008-7092/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-7094 is a medium-severity denial of service vulnerability in n/a, published on 26 Aug 2009. 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-7094 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-7094/ (Markdown: https://insights.sbomify.com/CVE-2008-7094/index.md)
```

## Sources

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

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