CVE-2014-0782
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStack-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStack-based buffer overflow in BKESimmgr.exe within the Expanded Test Functions package of Yokogawa CENTUM CS 1000, CENTUM CS 3000, CENTUM VP, Exaopc, and B/M9000 products allows remote attackers to execute arbitrary code via crafted network packets.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.05.01all versionsall versionsall versions<= 2.23.00all versions<= 3.09.50all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Complete
AV:N/AC:M/Au:N/C:P/I:P/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Yokogawa productsCheck system for Yokogawa CENTUM CS 1000, CENTUM CS 3000, CENTUM VP, Exaopc, or B/M9000 installations by inspecting installed programs or product directoriesAffected if Any of these products are installed and the version falls within affected ranges (B/m9000cs <=5.05.01 or all versions, CENTUM CS 3000 <=2.23.00 or all versions, CENTUM CS 3000 Entry Class <=3.09.50 or all versions, or CENTUM CS 1000 all versions)
-
Locate BKESimmgr.exeSearch for BKESimmgr.exe in Yokogawa product installation directories, typically under the installation root or within the Expanded Test Functions package subdirectoryAffected if BKESimmgr.exe is present on the system
-
Verify Expanded Test Functions package statusCheck whether the Expanded Test Functions package is loaded or enabled within the Yokogawa product configurationAffected if Expanded Test Functions package is enabled or loaded in the product configuration
-
Confirm product versionObtain the exact version number of the installed Yokogawa product using the product's built-in version information or license management tools, then compare against the affected version rangesAffected if Installed version is within the affected ranges: B/m9000cs <=5.05.01 or all versions, CENTUM CS 3000 <=2.23.00 or all versions, CENTUM CS 3000 Entry Class <=3.09.50 or all versions, CENTUM CS 1000 all versions
The system is likely affected if any vulnerable Yokogawa product is installed with BKESimmgr.exe present and the Expanded Test Functions package enabled, particularly if the product version falls within the affected ranges.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied patches for affected product versions, implement network segmentation to isolate ICS assets, and disable the Expanded Test Functions package if not operationally required.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0782 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data