# CVE-2019-16510: Use after free in n/a

> A use-after-free vulnerability in the libIEC61850 library allows attackers to potentially execute arbitrary code or cause a denial of service.

- **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:** 19 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wf63-pf87-93v4

## What is CVE-2019-16510?

CVE-2019-16510 is a high-severity use after free vulnerability in n/a, published on 19 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libIEC61850 through 1.3.3 has a use-after-free in MmsServer_waitReady in mms/iso_mms/server/mms_server.c, as demonstrated by server_example_goose.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2019-16510?

It affects 1 product.


Products: Mz-Automation Libiec61850.

## How do I fix CVE-2019-16510?

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

## Is CVE-2019-16510 being exploited?

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

## 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-2019-16510 and fix it if it is affected.

What it is: CVE-2019-16510 is a high-severity use after free vulnerability in n/a, published on 19 Sep 2019. 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-2019-16510 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-2019-16510/ (Markdown: https://insights.sbomify.com/CVE-2019-16510/index.md)
```

## Sources

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

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