# CVE-2017-12694: Path traversal in SpiderControl SCADA Web Server

> An attacker can use a GET request to traverse directories and read system files in the SpiderControl SCADA Web Server.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 25 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-75g2-f8v5-xc7g

## What is CVE-2017-12694?

CVE-2017-12694 is a high-severity path traversal vulnerability in SpiderControl SCADA Web Server, published on 25 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Directory Traversal issue was discovered in SpiderControl SCADA Web Server. An attacker may be able to use a simple GET request to perform a directory traversal into system files.

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

## Which versions are affected by CVE-2017-12694?

It affects 1 product.


Products: Spidercontrol Scada Web Server.

## How do I fix CVE-2017-12694?

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

## Is CVE-2017-12694 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12694 and fix it if it is affected.

What it is: CVE-2017-12694 is a high-severity path traversal vulnerability in SpiderControl SCADA Web Server, published on 25 Aug 2017. 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-2017-12694 in the wild and no public exploit code.

Affected product: SpiderControl SCADA Web Server. 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-2017-12694/ (Markdown: https://insights.sbomify.com/CVE-2017-12694/index.md)
```

## Sources

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

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