# CVE-2020-10615: Memory corruption in Triangle MicroWorks SCADA Data Gateway 3.02.0697 through 4.0.122, 2.41.0213 through 4.0.122

> Remote attackers can cause a denial-of-service condition in Triangle MicroWorks SCADA Data Gateway via a stack-based buffer overflow without authentication.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 15 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9w3w-gw8r-v3wj

## What is CVE-2020-10615?

CVE-2020-10615 is a high-severity memory corruption vulnerability in Triangle MicroWorks SCADA Data Gateway 3.02.0697 through 4.0.122, 2.41.0213 through 4.0.122, published on 15 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Triangle MicroWorks SCADA Data Gateway 3.02.0697 through 4.0.122, 2.41.0213 through 4.0.122 allows remote attackers cause a denial-of-service condition due to a lack of proper validation of the length of user-supplied data, prior to copying it to a fixed-length stack-based buffer. Authentication is not required to exploit this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Trianglemicroworks Scada Data Gateway.

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

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

## Is CVE-2020-10615 being exploited?

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

## Other vulnerabilities in Triangle MicroWorks SCADA Data Gateway 3.02.0697 through 4.0.122, 2.41.0213 through 4.0.122

- [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-2020-10615 and fix it if it is affected.

What it is: CVE-2020-10615 is a high-severity memory corruption vulnerability in Triangle MicroWorks SCADA Data Gateway 3.02.0697 through 4.0.122, 2.41.0213 through 4.0.122, published on 15 Apr 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-10615 in the wild and no public exploit code.

Affected product: Triangle MicroWorks SCADA Data Gateway 3.02.0697 through 4.0.122, 2.41.0213 through 4.0.122. 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-10615/ (Markdown: https://insights.sbomify.com/CVE-2020-10615/index.md)
```

## Sources

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

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