# CVE-2020-15158: Heap buffer overflow in libIEC61850

> An integer underflow in libIEC61850 allows remote attackers to cause a heap buffer overflow, leading to application crashes or remote code execution.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pq77-fmf7-hjw8

## What is CVE-2020-15158?

CVE-2020-15158 is a high-severity vulnerability in mz-automation libiec61850, published on 26 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In libIEC61850 before version 1.4.3, when a message with COTP message length field with value < 4 is received an integer underflow will happen leading to heap buffer overflow. This can cause an application crash or on some platforms even the execution of remote code. If your application is used in open networks or there are untrusted nodes in the network it is highly recommend to apply the patch. This was patched with commit 033ab5b. Users of version 1.4.x should upgrade to version 1.4.3 when available. As a workaround changes of commit 033ab5b can be applied to older versions.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound)), CWE-122 (Heap-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Mz-Automation Libiec61850.

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

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

## Is CVE-2020-15158 being exploited?

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

## Other vulnerabilities in mz-automation libiec61850

- [CVE-2022-2970](https://insights.sbomify.com/CVE-2022-2970/): MZ Automation libIEC61850 Stack-Based Buffer Overflow (critical 10.0)
- [CVE-2022-2972](https://insights.sbomify.com/CVE-2022-2972/): MZ Automation libIEC61850 Stack-Based Buffer Overflow (critical 10.0)
- [CVE-2024-45970](https://insights.sbomify.com/CVE-2024-45970/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-45971](https://insights.sbomify.com/CVE-2024-45971/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-19185](https://insights.sbomify.com/CVE-2018-19185/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-15158 is a high-severity vulnerability in mz-automation libiec61850, published on 26 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-15158 in the wild and no public exploit code.

Affected product: mz-automation libiec61850. 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-15158/ (Markdown: https://insights.sbomify.com/CVE-2020-15158/index.md)
```

## Sources

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

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