# CVE-2008-7093: Path traversal in n/a

> Remote attackers can create arbitrary files or list arbitrary files via directory traversal in Unica Affinium Campaign.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w6h2-q33g-f7x5

## What is CVE-2008-7093?

CVE-2008-7093 is a medium-severity path traversal vulnerability in n/a, published on 26 Aug 2009. It can be exploited over the network, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in Unica Affinium Campaign 7.2.1.0.55 allow remote attackers to (1) create arbitrary directories or files via a .. (dot dot) in the folder name in the new folder functionality or (2) list arbitrary files via a crafted request to Campaign/CampaignListener.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Unica Affinium Campaign.

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

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

## Is CVE-2008-7093 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-7094](https://insights.sbomify.com/CVE-2008-7094/): Denial of service in n/a (medium 5.0)
- [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-7093 and fix it if it is affected.

What it is: CVE-2008-7093 is a medium-severity path traversal vulnerability in n/a, published on 26 Aug 2009. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-7093 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-7093/ (Markdown: https://insights.sbomify.com/CVE-2008-7093/index.md)
```

## Sources

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

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