dbcve.org
Centum Cs 1000 FirmwareOperating system · Yokogawa

CVE-2015-5627

CRITICAL · 9.8 CVSS v3.1 Published 2020-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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 (process outage) 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 · high confidence

Stack-based buffer overflow in multiple Yokogawa industrial control software products (CENTUM, ProSafe-RS, Exaopc, Exaquantum, Exapilot, Exaplog, FAST/TOOLS, and related OPC servers and tools). Remote attackers can cause denial of service via crafted packets without authentication.

MitigationApply vendor patches for all affected products; for systems where patches are unavailable, isolate vulnerable systems on dedicated network segments and implement network-based filtering to block malformed 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
Centum Cs 1000 FirmwareOperating system
Affected:<= r3.08.70
Centum Cs 3000 FirmwareOperating system
Affected:<= r3.09.50
Centum Cs 3000 Entry FirmwareOperating system
Affected:<= r3.09.50
Centum Vp FirmwareOperating system
Affected:<= r5.04.20
Centum Vp Entry FirmwareOperating system
Affected:<= r5.04.20
Prosafe Rs FirmwareOperating system
Affected:<= r3.02.10
ExaopcApplication
Affected:<= r3.72.00
ExapilotApplication
Affected:<= r3.96.10

CVSS 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Yokogawa products
    Review system inventory or check installed programs for Yokogawa CENTUM, ProSafe-RS, Exaopc, Exapilot, FAST/TOOLS, Exaquantum, Exaplog, or related OPC server components
    Affected if Any of these Yokogawa products are present on the system
  2. Check firmware version for CENTUM CS 1000
    Access the control system interface or firmware management tool and retrieve the firmware version number
    Affected if Firmware version is r3.08.70 or lower
  3. Check firmware version for CENTUM CS 3000 or CS 3000 Entry
    Access the control system interface or firmware management tool and retrieve the firmware version number
    Affected if Firmware version is r3.09.50 or lower
  4. Check firmware version for CENTUM VP or VP Entry
    Access the control system interface or firmware management tool and retrieve the firmware version number
    Affected if Firmware version is r5.04.20 or lower
  5. Check firmware version for ProSafe-RS
    Access the safety system management interface and retrieve the firmware version number
    Affected if Firmware version is r3.02.10 or lower
  6. Check software version for Exaopc or Exapilot
    Check the installed software version through the application properties, about dialog, or version information in the installation directory
    Affected if Exaopc version is r3.72.00 or lower, or Exapilot version is r3.96.10 or lower

You are affected if any Yokogawa CENTUM, ProSafe-RS, Exaopc, or Exapilot product is installed with a version/firmware at or below the affected ranges and the service is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for all affected products; for systems where patches are unavailable, isolate vulnerable systems on dedicated network segments and implement network-based filtering to block malformed packets.

Recommended fix Moderate confidence

Contact Yokogawa for version-specific fixed releases greater than r3.08.70 (CS1000), r3.09.50 (CS3000), r5.04.20 (VP), r3.02.10 (ProSafe-RS), r3.72.00 (Exaopc), r3.96.10 (Exapilot)

  1. 1. Identify the exact product model and current firmware version running in your environment from the affected product list (CENTUM CS 1000, CS 3000, CS 3000 Entry, CENTUM VP, CENTUM VP Entry, ProSafe-RS, Exaopc, Exapilot)
  2. 2. Contact Yokogawa technical support directly to obtain the specific patch or firmware update for your product
  3. 3. Request the security advisory or patch information from Yokogawa for CVE-2015-5627
  4. 4. Obtain the fixed firmware version from Yokogawa - the advisory should specify versions greater than those listed (r3.08.70 for CS1000, r3.09.50 for CS3000, r5.04.20 for VP, r3.02.10 for ProSafe-RS, r3.72.00 for Exaopc, r3.96.10 for Exapilot)
  5. 5. Test the firmware update in a non-production environment first
  6. 6. Schedule a maintenance window and apply the firmware update or patch
  7. 7. Verify the update was applied successfully and the vulnerability is remediated
  8. 8. Implement network segmentation and access controls as additional defense-in-depth measures
Caveat Industrial control system firmware updates may require process shutdown and can affect operational continuity; test thoroughly in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Centum Cs 1000 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-5627 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-5627 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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