dbcve.org
Centum Vp FirmwareOperating system · Yokogawa

CVE-2022-21194

CRITICAL · 9.8 CVSS v3.1 Published 2022-03-11
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
The following Yokogawa Electric products do not change the passwords of the internal Windows accounts from the initial configuration: CENTUM VP versions from R5.01.00 to R5.04.20 and versions from R6.01.00 to R6.08.0, Exaopc versions from R3.72.00 to R3.79.00.

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

Yokogawa CENTUM VP (R5.01.00-R5.04.20, R6.01.00-R6.08.0) and Exaopc (R3.72.00-R3.79.00) ship with unchanged default passwords for internal Windows accounts from factory configuration. This critical default credential vulnerability allows remote unauthenticated attackers to gain elevated system access.

MitigationChange all default Windows account passwords on affected systems immediately. Follow vendor hardening guidelines and apply any available security patches to remediate this default credential issue.

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 Vp FirmwareOperating system
Affected:>= r5.01.00, <= r5.04.20>= r6.01.00, < r6.09.00
Centum Vp Entry FirmwareOperating system
Affected:>= r4.01.00, <= r4.03.00>= r5.01.00, <= r5.04.20>= r6.01.00, < r6.09.00
ExaopcApplication
Affected:>= r3.72.00, < r3.80.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
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 CENTUM VP firmware version
    Access the system engineering console or check the product's version information panel (typically found in the About or System Information section of the CENTUM VP interface). Alternatively, check the Windows registry or installation directories for version files.
    Affected if The installed version falls within R5.01.00-R5.04.20, R6.01.00-R6.08.0, or R6.01.00-R6.09.00 (depending on exact version numbering used)
  2. Identify installed CENTUM VP Entry firmware version
    Access the system information from the Entry console or check installation directories for version metadata.
    Affected if The installed version falls within R4.01.00-R4.03.00, R5.01.00-R5.04.20, or R6.01.00-R6.08.0
  3. Identify installed Exaopc version
    Check the Exaopc installation folder for version information, or access the product's system information through its management interface.
    Affected if The installed version falls within R3.72.00-R3.79.00
  4. Verify Windows account passwords have been changed
    Use Windows Local Users and Groups management (lusrmgr.msc) or PowerShell Get-LocalUser cmdlet to list local accounts. Compare account passwords against documented default credentials in vendor hardening documentation or check if any factory default account names still exist with their original passwords.
    Affected if Any default Windows system accounts from factory configuration retain their original default passwords, or unknown/unexpected accounts with default credentials exist

Your environment is affected if any Yokogawa CENTUM VP or Exaopc installation runs a version within the listed ranges AND retains default Windows account passwords from factory configuration.

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

Change all default Windows account passwords on affected systems immediately. Follow vendor hardening guidelines and apply any available security patches to remediate this default credential issue.

Recommended fix High confidence

Centum VP: upgrade to R6.09.00 or later; Centum VP Entry: upgrade to R6.09.00 or later; Exaopc: upgrade to R3.80.00 or later

  1. 1. Identify all affected Yokogawa products (Centum VP, Centum VP Entry, Exaopc) currently deployed in the environment
  2. 2. Obtain the fixed software releases: Centum VP R6.09.00 or later, Centum VP Entry R6.09.00 or later, Exaopc R3.80.00 or later
  3. 3. Download the updated firmware/software from Yokogawa's official support portal (web-material3.yokogawa.com) or contact Yokogawa customer support
  4. 4. Schedule a maintenance window as the upgrade may require system downtime
  5. 5. Create a full backup of the current system configuration and data
  6. 6. Review upgrade documentation and release notes for any prerequisites
  7. 7. Apply the firmware/software upgrade to each affected component following Yokogawa's official installation procedures
  8. 8. After upgrade, verify that internal Windows account passwords have been changed from initial configuration
Caveat Review Yokogawa release notes for compatibility with dependent systems and any feature changes between current and fixed versions before upgrading

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

Fix this in Centum Vp Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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