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

> Remote attackers can exploit path traversal in ActiveX controls to overwrite files, potentially achieving code execution via startup folder manipulation.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-89pq-qvjv-f582

## What is CVE-2008-2015?

CVE-2008-2015 is a critical path traversal vulnerability in n/a, published on 30 Apr 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple absolute path traversal vulnerabilities in certain ActiveX controls in WatchFire AppScan 7.0 allow remote attackers to create or overwrite arbitrary files via a full pathname in the argument to the (1) CompactSave and (2) SaveSession method in one control, and the (3) saveRecordedExploreToFile method in a different control.  NOTE: this can be leveraged for code execution by writing to a Startup folder.

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

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

It affects 1 product.


Products: Watchfire Appscan.

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

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

## Is CVE-2008-2015 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-2015 exists.

Public exploit code:

- Watchfire Appscan 7.0 - ActiveX Multiple Insecure Methods (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2015 is a critical path traversal vulnerability in n/a, published on 30 Apr 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-2015 exists.

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-2015/ (Markdown: https://insights.sbomify.com/CVE-2008-2015/index.md)
```

## Sources

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

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