# CVE-2009-2047: Path traversal in n/a

> Authenticated attackers can read, modify, or delete arbitrary files via directory traversal in the Cisco Unified Contact Center Express administration interface.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hcx9-6rrj-jfqh

## What is CVE-2009-2047?

CVE-2009-2047 is a critical path traversal vulnerability in n/a, published on 16 Jul 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in the Administration interface in Cisco Customer Response Solutions (CRS) before 7.0(1) SR2 in Cisco Unified Contact Center Express (aka CCX) server allows remote authenticated users to read, modify, or delete arbitrary files via unspecified vectors.

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

## Which versions are affected by CVE-2009-2047?

It affects 6 products.


Products: Cisco Crs, Cisco Customer Response Applications, Cisco Ip Qm, Cisco Unified Ccx, Cisco Unified Ip Contact Center Express, Cisco Unified Ip Ivr.

## How do I fix CVE-2009-2047?

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

## Is CVE-2009-2047 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2048](https://insights.sbomify.com/CVE-2009-2048/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2047 and fix it if it is affected.

What it is: CVE-2009-2047 is a critical path traversal vulnerability in n/a, published on 16 Jul 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-2047 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-2009-2047/ (Markdown: https://insights.sbomify.com/CVE-2009-2047/index.md)
```

## Sources

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

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