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

> Remote attackers with admin access can list arbitrary directories via path traversal in the file browser, exposing sensitive file structures.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cgcr-5g8h-p7j5

## What is CVE-2008-5997?

CVE-2008-5997 is a high-severity path traversal vulnerability in n/a, published on 28 Jan 2009. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Absolute path traversal vulnerability in admin/fileKontrola/browser.asp in Omnicom Content Platform (OCP) 2.0 allows remote attackers to list arbitrary directories via a full pathname in the root parameter.

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

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

It affects 1 product.


Products: Ocp2 Omnicom Content Platform.

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

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

## Is CVE-2008-5997 being exploited?

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

Public exploit code:

- Omnicom Content Platform - 'browser.asp' Directory Traversal (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-5997 is a high-severity path traversal vulnerability in n/a, published on 28 Jan 2009. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5997 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-5997/ (Markdown: https://insights.sbomify.com/CVE-2008-5997/index.md)
```

## Sources

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

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