dbcve.org
Centum Cs 3000 FirmwareOperating system · Yokogawa

CVE-2018-16196

HIGH · 7.5 CVSS v3.0 Published 2019-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Multiple Yokogawa products that contain Vnet/IP Open Communication Driver (CENTUM CS 3000(R3.05.00 - R3.09.50), CENTUM CS 3000 Entry Class(R3.05.00 - R3.09.50), CENTUM VP(R4.01.00 - R6.03.10), CENTUM VP Entry Class(R4.01.00 - R6.03.10), Exaopc(R3.10.00 - R3.75.00), PRM(R2.06.00 - R3.31.00), ProSafe-RS(R1.02.00 - R4.02.00), FAST/TOOLS(R9.02.00 - R10.02.00), B/M9000 VP(R6.03.01 - R8.01.90)) allows remote attackers to cause a denial of service attack that may result in stopping Vnet/IP Open Communication Driver's communication via unspecified vectors.

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

A denial of service vulnerability in the Vnet/IP Open Communication Driver affecting multiple Yokogawa industrial control products (CENTUM CS 3000, CENTUM VP, Exaopc, PRM, ProSafe-RS, FAST/TOOLS, B/M9000 VP across specified version ranges). Remote attackers can exploit unspecified vectors to stop the Vnet/IP driver's communication, potentially disrupting industrial operations.

MitigationApply vendor-supplied patches to affected Vnet/IP Open Communication Driver installations. Prior to patching in production environments, validate patches in isolated testing environments to ensure operational continuity.

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 3000 FirmwareOperating system
Affected:>= r3.05.00, <= r3.09.50
Centum Cs 3000 Entry ClassApplication
Affected:>= r3.05.00, <= r3.09.50
Centum Vp FirmwareOperating system
Affected:>= r4.01.00, <= r6.03.10
Centum Vp Entry ClassApplication
Affected:>= r4.01.00, <= r6.03.10
B\/m9000 VpApplication
Affected:>= r6.03.01, <= r8.01.90
ExaopcApplication
Affected:>= r3.10.00, <= r3.75.00
Fast\/toolsApplication
Affected:>= r9.02.00, <= r10.02.00
Plant Resource ManagerApplication
Affected:>= r2.06.00, <= r3.31.00

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 product
    Review system inventory, installed programs list, or consult product documentation to determine which Yokogawa industrial control software is running (CENTUM CS 3000, CENTUM VP, Exaopc, PRM, FAST/TOOLS, B/M9000 VP, or ProSafe-RS)
    Affected if No Yokogawa products from the affected list are installed
  2. Locate product version information
    Access the product's About or Version information panel within the software interface, check system registry entries for the product version, or review version files in the product installation directory
    Affected if Unable to determine the product version
  3. Compare version against affected ranges
    Match the installed version number to the specific ranges: CENTUM CS 3000 (r3.05.00 to r3.09.50), CENTUM VP (r4.01.00 to r6.03.10), B/M9000 VP (r6.03.01 to r8.01.90), Exaopc (r3.10.00 to r3.75.00), FAST/TOOLS (r9.02.00 to r10.02.00), PRM (r2.06.00 to r3.31.00)
    Affected if Installed version falls within the listed range for that product
  4. Verify Vnet/IP driver is active
    Check the control system configuration or driver status for the Vnet/IP Open Communication Driver - look in the product's communication settings, driver management console, or system control panel
    Affected if Vnet/IP driver is loaded and actively handling communications

Your environment is affected if any Yokogawa product from the list is installed with a version matching the specified range AND the Vnet/IP Open Communication Driver is enabled and handling communications.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches to affected Vnet/IP Open Communication Driver installations. Prior to patching in production environments, validate patches in isolated testing environments to ensure operational continuity.

Fix this in Centum Cs 3000 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-16196 — 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-2018-16196 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