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

> Remote attackers can read arbitrary files on Indusoft and Advantech Studio servers via absolute path traversal in the web server component.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4f67-fhjj-9h87

## What is CVE-2013-1627?

CVE-2013-1627 is a high-severity path traversal vulnerability in n/a, published on 11 Mar 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Absolute path traversal vulnerability in NTWebServer.exe in Indusoft Studio 7.0 and earlier and Advantech Studio 7.0 and earlier allows remote attackers to read arbitrary files via a full pathname in an argument to the sub_401A90 CreateFileW function.

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

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

It affects 2 products.


Products: Advantech Advantech Studio, Indusoft Web Studio.

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

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

## Is CVE-2013-1627 being exploited?

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

Public exploit code:

- Advantech Studio 7.0 - SCADA/HMI Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-0488](https://insights.sbomify.com/CVE-2011-0488/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-0340](https://insights.sbomify.com/CVE-2011-0340/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1627 is a high-severity path traversal vulnerability in n/a, published on 11 Mar 2013. 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-2013-1627 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-2013-1627/ (Markdown: https://insights.sbomify.com/CVE-2013-1627/index.md)
```

## Sources

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

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