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

> Remote attackers can execute arbitrary file operations via directory traversal in Siemens WinCC HMI systems when Transfer Mode is enabled.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2012
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3ppq-p8g9-x6rg

## What is CVE-2011-4876?

CVE-2011-4876 is a critical path traversal vulnerability in n/a, published on 3 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in HmiLoad in the runtime loader in Siemens WinCC flexible 2004, 2005, 2007, and 2008; WinCC V11 (aka TIA portal); the TP, OP, MP, Comfort Panels, and Mobile Panels SIMATIC HMI panels; WinCC V11 Runtime Advanced; and WinCC flexible Runtime, when Transfer Mode is enabled, allows remote attackers to execute, read, create, modify, or delete arbitrary files via a .. (dot dot) in a string.

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

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

It affects 5 products.


Products: Siemens Simatic Hmi Panels, Siemens Wincc, Siemens Wincc Flexible, Siemens Wincc Flexible Runtime, Siemens Wincc Runtime Advanced.

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

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

## Is CVE-2011-4876 being exploited?

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

Public exploit code:

- Siemens SIMATIC WinCC Flexible (Runtime) - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-4509](https://insights.sbomify.com/CVE-2011-4509/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2011-4513](https://insights.sbomify.com/CVE-2011-4513/): Code injection in n/a (critical 10.0)
- [CVE-2011-4514](https://insights.sbomify.com/CVE-2011-4514/): Auth bypass in n/a (critical 10.0)
- [CVE-2011-4508](https://insights.sbomify.com/CVE-2011-4508/): Auth bypass in n/a (critical 9.3)
- [CVE-2011-4875](https://insights.sbomify.com/CVE-2011-4875/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-4876 is a critical path traversal vulnerability in n/a, published on 3 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-4876 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-2011-4876/ (Markdown: https://insights.sbomify.com/CVE-2011-4876/index.md)
```

## Sources

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

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