# CVE-2013-0671: Path traversal in n/a

> Authenticated attackers can read HMI source code and scripts via directory traversal in Siemens WinCC TIA Portal.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-wq64-pr5g-jvr4

## What is CVE-2013-0671?

CVE-2013-0671 is a medium-severity path traversal vulnerability in n/a, published on 21 Mar 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in Siemens WinCC (TIA Portal) 11 allows remote authenticated users to read HMI web-application source code and user-defined scripts via a crafted URL.

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

## Which versions are affected by CVE-2013-0671?

It affects 1 product.


Products: Siemens Wincc Tia Portal.

## How do I fix CVE-2013-0671?

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

## Is CVE-2013-0671 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-4515](https://insights.sbomify.com/CVE-2011-4515/): Weak cryptography in n/a (medium 4.6)
- [CVE-2013-0667](https://insights.sbomify.com/CVE-2013-0667/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2013-0668](https://insights.sbomify.com/CVE-2013-0668/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2013-0670](https://insights.sbomify.com/CVE-2013-0670/): Other in n/a (medium 4.3)
- [CVE-2013-0669](https://insights.sbomify.com/CVE-2013-0669/): Denial of service in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0671 and fix it if it is affected.

What it is: CVE-2013-0671 is a medium-severity path traversal vulnerability in n/a, published on 21 Mar 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0671 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-2013-0671/ (Markdown: https://insights.sbomify.com/CVE-2013-0671/index.md)
```

## Sources

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

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