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

> Remote attackers can upload files to arbitrary locations via directory traversal in VMware Studio's web interface, potentially leading to code execution.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-65qh-vmj5-8hx8

## What is CVE-2009-2968?

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

### Official description

Directory traversal vulnerability in a support component in the web interface in VMware Studio 2.0 public beta before build 1017-185256 allows remote attackers to upload files to arbitrary locations via unspecified vectors.

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

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

It affects 1 product.


Products: Vmware Studio.

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

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

## Is CVE-2009-2968 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2667](https://insights.sbomify.com/CVE-2010-2667/): Command injection in n/a (medium 6.0)
- [CVE-2010-2427](https://insights.sbomify.com/CVE-2010-2427/): Privilege escalation in n/a (medium 4.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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