# CVE-2015-10123: Wago: Buffer Copy without Checking Size of Input in wbm of multiple products

> An attacker can trigger a buffer overflow in WAGO industrial controllers via crafted packets, leading to full device compromise when viewed by an authenticated user.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Mar 2024
- **Updated:** 23 Oct 2024
- **Also known as:** GHSA-6qmr-x8pc-q3r8

## What is CVE-2015-10123?

CVE-2015-10123 is a high-severity memory corruption vulnerability in WAGO Controller BACnet MS/TP, published on 13 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An unautheticated remote attacker could send specifically crafted packets to a affected device. If an authenticated user then views that data in a specific page of the web-based management a buffer overflow will be triggered to gain full access of the device.

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

## Which versions are affected by CVE-2015-10123?


## How do I fix CVE-2015-10123?

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

## Is CVE-2015-10123 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-10123 and fix it if it is affected.

What it is: CVE-2015-10123 is a high-severity memory corruption vulnerability in WAGO Controller BACnet MS/TP, published on 13 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-10123 in the wild and no public exploit code.

Affected product: WAGO Controller BACnet MS/TP. 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-2015-10123/ (Markdown: https://insights.sbomify.com/CVE-2015-10123/index.md)
```

## Sources

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

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