# CVE-2022-0369: Triangle MicroWorks SCADA Data Gateway Restore Workspace Directory Traversal Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code with SYSTEM privileges via directory traversal in the Restore Workspace feature, bypassing authentication.

- **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:** 7 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-jhmq-fqq2-2qvv

## What is CVE-2022-0369?

CVE-2022-0369 is a high-severity path traversal vulnerability in Triangle MicroWorks SCADA Data Gateway, published on 7 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Triangle MicroWorks SCADA Data Gateway Restore Workspace Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Triangle MicroWorks SCADA Data Gateway. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed.

The specific flaw exists within the Restore Workspace feature. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-17227.

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

## Which versions are affected by CVE-2022-0369?

It affects 1 product.


Products: Trianglemicroworks Scada Data Gateway.

## How do I fix CVE-2022-0369?

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

## Is CVE-2022-0369 being exploited?

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

## Other vulnerabilities in Triangle MicroWorks SCADA Data Gateway

- [CVE-2023-39457](https://insights.sbomify.com/CVE-2023-39457/): Triangle MicroWorks SCADA Data Gateway Missing Authentication Vulnerability (critical 9.8)
- [CVE-2020-10611](https://insights.sbomify.com/CVE-2020-10611/): Memory corruption in Triangle MicroWorks SCADA Data Gateway 3.02.0697 through 4.0.122, 2.41.0213 through 4.0.122 (critical 9.8)
- [CVE-2023-2186](https://insights.sbomify.com/CVE-2023-2186/): Other in SCADA Data Gateway (high 8.2)
- [CVE-2023-39459](https://insights.sbomify.com/CVE-2023-39459/): Triangle MicroWorks SCADA Data Gateway Directory Traversal Arbitrary File Creation Vulnerability (high 7.8)
- [CVE-2023-39465](https://insights.sbomify.com/CVE-2023-39465/): Triangle MicroWorks SCADA Data Gateway Use of Hard-coded Cryptograhic Key Information Disclosure Vulnerability (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0369 and fix it if it is affected.

What it is: CVE-2022-0369 is a high-severity path traversal vulnerability in Triangle MicroWorks SCADA Data Gateway, published on 7 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0369 in the wild and no public exploit code.

Affected product: Triangle MicroWorks SCADA Data Gateway. 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-2022-0369/ (Markdown: https://insights.sbomify.com/CVE-2022-0369/index.md)
```

## Sources

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

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