# CVE-2010-2627: Path traversal in n/a

> Remote servers can overwrite arbitrary client files via directory traversal in Refractor 2 engine URLs, affecting Battlefield 2 and 2142 players.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 2 Jul 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-p5gp-p59f-xww7

## What is CVE-2010-2627?

CVE-2010-2627 is a medium-severity path traversal vulnerability in n/a, published on 2 Jul 2010. 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 directory traversal vulnerabilities in the Refractor 2 engine, as used in Battlefield 2 1.50 (1.5.3153-802.0) and earlier, and Battlefield 2142 (1.10.48.0) and earlier, allow remote servers to overwrite arbitrary files on the client via "..\" (dot dot backslash) sequences in URLs for the (1) sponsor or (2) community logos, and other URLs related to (3) DemoDownloadURL, (4) DemoIndexURL and (5) CustomMapsURL.

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

## Which versions are affected by CVE-2010-2627?

It affects 2 products.


Products: Ea Battlefield 2, Ea Battlefield 2142.

## How do I fix CVE-2010-2627?

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

## Is CVE-2010-2627 being exploited?

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

Public exploit code:

- EA Battlefield 2 / Battlefield 2142 - Multiple Arbitrary File Upload Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2627 and fix it if it is affected.

What it is: CVE-2010-2627 is a medium-severity path traversal vulnerability in n/a, published on 2 Jul 2010. 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-2010-2627 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-2010-2627/ (Markdown: https://insights.sbomify.com/CVE-2010-2627/index.md)
```

## Sources

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

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