# CVE-2011-1932: Path traversal in n/a

> Remote attackers can overwrite arbitrary files via path traversal in Widelands Internet game file transfers.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Dec 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-1932, GHSA-x33h-x48f-38q6

## What is CVE-2011-1932?

CVE-2011-1932 is a medium-severity path traversal vulnerability in n/a, published on 5 Dec 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in io/filesystem/filesystem.cc in Widelands before 15.1 might allow remote attackers to overwrite arbitrary files via . (dot) characters in a pathname that is used for a file transfer in an Internet game.

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

## Which versions are affected by CVE-2011-1932?

It affects 1 product.


Products: Widelands Widelands.

## How do I fix CVE-2011-1932?

Upgrade to a fixed version.

## Is CVE-2011-1932 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-4675](https://insights.sbomify.com/CVE-2011-4675/): Path traversal in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1932 and fix it if it is affected.

What it is: CVE-2011-1932 is a medium-severity path traversal vulnerability in n/a, published on 5 Dec 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-1932 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-2011-1932/ (Markdown: https://insights.sbomify.com/CVE-2011-1932/index.md)
```

## Sources

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

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