# CVE-2020-7497: Path traversal in EcoStruxure Operator Terminal Expert 3.1 Service Pack 1 and prior (formerly known as Vijeo XD)

> A path traversal flaw in EcoStruxure Operator Terminal Expert allows arbitrary code execution upon system startup, posing a risk to industrial control environments.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vh6q-rcrv-qvjc

## What is CVE-2020-7497?

CVE-2020-7497 is a critical path traversal vulnerability in EcoStruxure Operator Terminal Expert 3.1 Service Pack 1 and prior (formerly known as Vijeo XD), published on 16 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability exists in EcoStruxure Operator Terminal Expert 3.1 Service Pack 1 and prior (formerly known as Vijeo XD)which could cause arbitrary application execution when the computer starts.

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

## Which versions are affected by CVE-2020-7497?

It affects 1 product.


Products: Schneider-Electric Ecostruxure Operator Terminal Expert.

## How do I fix CVE-2020-7497?

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

## Is CVE-2020-7497 being exploited?

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

## Other vulnerabilities in EcoStruxure Operator Terminal Expert 3.1 Service Pack 1 and prior (formerly known as Vijeo XD)

- [CVE-2020-28221](https://insights.sbomify.com/CVE-2020-28221/): Code injection in EcoStruxure™ Operator Terminal Expert 3.1 Service Pack 1A and prior running on Harmony HMIs HMIST6 Series, HMIG3U in HMIGTU Series, HMISTO Series and Pro-face BLUE 3.1 Service Pack 1A and prior running on Pro-face HMIs: ST6000 Series, SP-5B41 in SP5000 Series, GP4100 Series (critical 9.8)
- [CVE-2023-1049](https://insights.sbomify.com/CVE-2023-1049/): Code injection in EcoStruxure™ Operator Terminal Expert (high 7.8)
- [CVE-2020-7493](https://insights.sbomify.com/CVE-2020-7493/): SQL injection in EcoStruxure Operator Terminal Expert 3.1 Service Pack 1 and prior (formerly known as Vijeo XD) (high 7.8)
- [CVE-2020-7494](https://insights.sbomify.com/CVE-2020-7494/): Path traversal in EcoStruxure Operator Terminal Expert 3.1 Service Pack 1 and prior (formerly known as Vijeo XD) (high 7.8)
- [CVE-2022-41666](https://insights.sbomify.com/CVE-2022-41666/): Security feature bypass in EcoStruxure Operator Terminal Expert (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7497 and fix it if it is affected.

What it is: CVE-2020-7497 is a critical path traversal vulnerability in EcoStruxure Operator Terminal Expert 3.1 Service Pack 1 and prior (formerly known as Vijeo XD), published on 16 Jun 2020. 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-2020-7497 in the wild and no public exploit code.

Affected product: EcoStruxure Operator Terminal Expert 3.1 Service Pack 1 and prior (formerly known as Vijeo XD). 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-2020-7497/ (Markdown: https://insights.sbomify.com/CVE-2020-7497/index.md)
```

## Sources

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

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