# CVE-2015-5626: Memory corruption in B/M9000 VP

> Remote attackers can cause a denial of service in Yokogawa industrial control systems via a crafted packet exploiting a stack-based buffer overflow.

- **Severity:** Critical 9.8 (`CVSS:3.1/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 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gmf6-3628-28f2

## What is CVE-2015-5626?

CVE-2015-5626 is a critical memory corruption vulnerability in Yokogawa B/M9000 VP, published on 5 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in Yokogawa CENTUM CS 1000 R3.08.70 and earlier, CENTUM CS 3000 R3.09.50 and earlier, CENTUM CS 3000 Entry R3.09.50 and earlier, CENTUM VP R5.04.20 and earlier, CENTUM VP Entry R5.04.20 and earlier, ProSafe-RS R3.02.10 and earlier, Exaopc R3.72.00 and earlier, Exaquantum R2.85.00 and earlier, Exaquantum/Batch R2.50.30 and earlier, Exapilot R3.96.10 and earlier, Exaplog R3.40.00 and earlier, Exasmoc R4.03.20 and earlier, Exarqe R4.03.20 and earlier, Field Wireless Device OPC Server R2.01.02 and earlier, PRM R3.12.00 and earlier, STARDOM VDS R7.30.01 and earlier, STARDOM OPC Server for Windows R3.40 and earlier, FAST/TOOLS R10.01 and earlier, B/M9000CS R5.05.01 and earlier, B/M9000 VP R7.03.04 and earlier, and FieldMate R1.01 or R1.02 allows remote attackers to cause a denial of service (network-communications outage) via a crafted packet.

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

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

It affects 21 products.


Products: Yokogawa B\/M9000 Vp Firmware, Yokogawa B\/M9000cs Firmware, Yokogawa Centum Cs 1000 Firmware, Yokogawa Centum Cs 3000 Entry Firmware, Yokogawa Centum Cs 3000 Firmware, Yokogawa Centum Vp Entry Firmware, Yokogawa Centum Vp Firmware, Yokogawa Exaopc, Yokogawa Exapilot, Yokogawa Exaplog, Yokogawa Exaquantum, Yokogawa Exaquantum\/Batch, Yokogawa Exarqe, Yokogawa Exasmoc, Yokogawa Field Wireless Device Opc Server, Yokogawa Fieldmate, Yokogawa Plant Resource Manager, Yokogawa Prosafe-Rs Firmware, Yokogawa Scada Software \(Fast\/Tools\), Yokogawa Stardom Opc Server and 1 more.

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

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

## Is CVE-2015-5626 being exploited?

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

## Other vulnerabilities in Yokogawa B/M9000 VP

- [CVE-2015-5627](https://insights.sbomify.com/CVE-2015-5627/): Memory corruption in B/M9000 VP (critical 9.8)
- [CVE-2015-5628](https://insights.sbomify.com/CVE-2015-5628/): Memory corruption in B/M9000 VP (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-5626 is a critical memory corruption vulnerability in Yokogawa B/M9000 VP, published on 5 Feb 2020. 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-2015-5626 in the wild and no public exploit code.

Affected product: Yokogawa B/M9000 VP. 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-5626/ (Markdown: https://insights.sbomify.com/CVE-2015-5626/index.md)
```

## Sources

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

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