# CVE-2018-18957: Memory corruption in n/a

> A stack-based buffer overflow in libIEC61850 allows attackers to execute arbitrary code or cause denial of service via crafted GOOSE messages.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 5 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8j92-r28v-983h

## What is CVE-2018-18957?

CVE-2018-18957 is a critical memory corruption vulnerability in n/a, published on 5 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue has been found in libIEC61850 v1.3. It is a stack-based buffer overflow in prepareGooseBuffer in goose/goose_publisher.c.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2018-18957?

It affects 1 product.


Products: Mz-Automation Libiec61850.

## How do I fix CVE-2018-18957?

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

## Is CVE-2018-18957 being exploited?

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

Public exploit code:

- libiec61850 1.3 - Stack Based Buffer Overflow (exploitdb)
- libiec61850 1.3 - Stack Based Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

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

What it is: CVE-2018-18957 is a critical memory corruption vulnerability in n/a, published on 5 Nov 2018. 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-2018-18957 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-2018-18957/ (Markdown: https://insights.sbomify.com/CVE-2018-18957/index.md)
```

## Sources

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

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