# CVE-2014-0782: Yokogawa CENTUM CS 3000 Stack-based Buffer Overflow

> Remote attackers can execute arbitrary code via a crafted packet targeting the Expanded Test Functions package in Yokogawa CENTUM systems.

- **Severity:** High 8.3 (`AV:N/AC:M/Au:N/C:P/I:P/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2014
- **Updated:** 25 Sep 2025
- **Also known as:** GHSA-fhrf-qc9p-xhrg

## What is CVE-2014-0782?

CVE-2014-0782 is a high-severity memory corruption vulnerability in Yokogawa CENTUM CS 3000, published on 16 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in BKESimmgr.exe in the Expanded Test Functions package in Yokogawa CENTUM CS 1000, CENTUM CS 3000 Entry Class R3.09.50 and earlier, CENTUM VP R5.03.00 and earlier, CENTUM VP Entry Class R5.03.00 and earlier, Exaopc R3.71.02 and earlier, B/M9000CS R5.05.01 and earlier, and B/M9000 VP R7.03.01 and earlier allows remote attackers to execute arbitrary code via a crafted packet.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2014-0782?

It affects 15 products.


Products: Yokogawa B\/M9000 Vp, Yokogawa B\/M9000 Vp Software, Yokogawa B\/M9000cs, Yokogawa B\/M9000cs Software, Yokogawa Centum Cs 1000, Yokogawa Centum Cs 1000 Software, Yokogawa Centum Cs 3000, Yokogawa Centum Cs 3000 Entry Class, Yokogawa Centum Cs 3000 Entry Class Software, Yokogawa Centum Cs 3000 Software, Yokogawa Centum Vp, Yokogawa Centum Vp Entry Class, Yokogawa Centum Vp Entry Class Software, Yokogawa Centum Vp Software, Yokogawa Exaopc.

## How do I fix CVE-2014-0782?

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

## Is CVE-2014-0782 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-0782 exists.

Public exploit code:

- Yokogawa CS3000 BKESimmgr.exe Buffer Overflow (metasploit)
- Yokogawa CS3000 - 'BKESimmgr.exe' Remote Buffer Overflow (Metasploit) (exploitdb)

## Other vulnerabilities in Yokogawa CENTUM CS 3000

- [CVE-2022-26034](https://insights.sbomify.com/CVE-2022-26034/): Auth bypass in CENTUM VP series with VP6E5000(AD Suite Engineering ServerFunction) installed and B/M9000 VP (critical 9.1)
- [CVE-2022-30707](https://insights.sbomify.com/CVE-2022-30707/): Information disclosure in CAMS for HIS (high 8.8)
- [CVE-2014-3888](https://insights.sbomify.com/CVE-2014-3888/): Memory corruption in n/a (high 8.3)
- [CVE-2023-26593](https://insights.sbomify.com/CVE-2023-26593/): Hardcoded credentials in CENTUM series (high 7.8)
- [CVE-2022-27188](https://insights.sbomify.com/CVE-2022-27188/): Command injection in CENTUM VP series with VP6E5150(Graphic Builder) installed and B/M9000 VP (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0782 and fix it if it is affected.

What it is: CVE-2014-0782 is a high-severity memory corruption vulnerability in Yokogawa CENTUM CS 3000, published on 16 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-0782 exists.

Affected product: Yokogawa CENTUM CS 3000. 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-2014-0782/ (Markdown: https://insights.sbomify.com/CVE-2014-0782/index.md)
```

## Sources

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

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