# CVE-2007-0100: Path traversal in n/a

> Remote attackers can overwrite arbitrary files on the client system by operating a malicious server or modifying server-side configuration.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 8 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-79v5-9c98-r9cr

## What is CVE-2007-0100?

CVE-2007-0100 is a critical path traversal vulnerability in n/a, published on 8 Jan 2007. 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

The Perforce client does not restrict the set of files that it overwrites upon receiving a request from the server, which allows remote attackers to overwrite arbitrary files by modifying the client config file on the server, or by operating a malicious server.

## Which versions are affected by CVE-2007-0100?

It affects 1 product.


Products: Perforce Perforce Client.

## How do I fix CVE-2007-0100?

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

## Is CVE-2007-0100 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0100 and fix it if it is affected.

What it is: CVE-2007-0100 is a critical path traversal vulnerability in n/a, published on 8 Jan 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-0100 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-2007-0100/ (Markdown: https://insights.sbomify.com/CVE-2007-0100/index.md)
```

## Sources

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

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