# CVE-2024-34057: Memory corruption in n/a

> A buffer overflow in the IEC 61850 client library allows attackers to cause a denial of service by sending crafted messages.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 18 Sep 2024
- **Updated:** 19 Sep 2024
- **Also known as:** GHSA-94j8-54mg-394v

## What is CVE-2024-34057?

CVE-2024-34057 is a high-severity memory corruption vulnerability in n/a, published on 18 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Triangle Microworks TMW IEC 61850 Client source code libraries before 12.2.0 lack a buffer size check when processing received messages. The resulting buffer overflow can cause a crash, resulting in a denial of service.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-34057?

It affects 6 products.


Products: Siemens Sicam A8000 Firmware, Siemens Sicam Egs Firmware, Siemens Sicam S8000, Siemens Sicam Scc Firmware, Siemens Sitipe At, Trianglemicroworks Iec 61850 Source Code Library.

## How do I fix CVE-2024-34057?

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

## Is CVE-2024-34057 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15781](https://insights.sbomify.com/CVE-2020-15781/): Cross-site scripting in SICAM WEB firmware for SICAM A8000 RTUs (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34057 and fix it if it is affected.

What it is: CVE-2024-34057 is a high-severity memory corruption vulnerability in n/a, published on 18 Sep 2024. 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-2024-34057 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-2024-34057/ (Markdown: https://insights.sbomify.com/CVE-2024-34057/index.md)
```

## Sources

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

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