# CVE-2017-9970: File upload in n/a

> Remote attackers can upload malicious zip files to arbitrary directories, leading to remote code execution on Schneider Electric StruxureOn Gateways.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6683-fqx9-gxhp

## What is CVE-2017-9970?

CVE-2017-9970 is a high-severity vulnerability in n/a, published on 12 Feb 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A remote code execution vulnerability exists in Schneider Electric's StruxureOn Gateway versions 1.1.3 and prior. Uploading a zip which contains carefully crafted metadata allows for the file to be uploaded to any directory on the host machine information which could lead to remote code execution.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Schneider-Electric Struxureon Gateway.

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

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

## Is CVE-2017-9970 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9970 is a high-severity vulnerability in n/a, published on 12 Feb 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9970 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-2017-9970/ (Markdown: https://insights.sbomify.com/CVE-2017-9970/index.md)
```

## Sources

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

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