dbcve.org
B\/m9000 VpApplication · Yokogawa

CVE-2022-27188

HIGH · 7.8 CVSS v3.1 Published 2022-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
OS command injection vulnerability exists in CENTUM VP R4.01.00 to R4.03.00, CENTUM VP Small R4.01.00 to R4.03.00, CENTUM VP Basic R4.01.00 to R4.03.00, and B/M9000 VP R6.01.01 to R6.03.02, which may allow an attacker who can access the computer where the affected product is installed to execute an arbitrary OS command by altering a file generated using Graphic Builder.

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

OS command injection vulnerability in Yokogawa CENTUM VP and B/M9000 VP allows local attackers with computer access to execute arbitrary OS commands by modifying files generated by Graphic Builder, a configuration tool for the HMI/SCADA system.

MitigationRestrict physical and logical access to systems running affected CENTUM VP versions; contact Yokogawa for patched versions or vendor guidance on securing Graphic Builder file handling.

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
B\/m9000 VpApplication
Affected:>= r6.01.01, <= r6.03.02
Centum VpApplication
Affected:>= r4.01.00, <= r4.03.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 product
    Check system inventory or installed programs for Yokogawa B/M9000 VP or CENTUM VP
    Affected if Product is either B/M9000 VP or CENTUM VP
  2. Determine the product version
    Use system information, installed programs list, or check version information in the Yokogawa application (typically via Help > About or check version files in the installation directory)
    Affected if Version is B/M9000 VP r6.01.01 through r6.03.02 inclusive, or CENTUM VP r4.01.00 through r4.03.00 inclusive
  3. Confirm Graphic Builder is installed and accessible
    Locate Graphic Builder executable in the Yokogawa installation directory (commonly in a 'GraphicBuilder' or 'GB' subfolder)
    Affected if Graphic Builder component is present on the system
  4. Check file permissions on Graphic Builder output files
    Examine file permissions on files generated by Graphic Builder (typically .gbf, .gbl or similar graphic configuration files in the project directory)
    Affected if Files are writable by users with computer access who should not have write permission

The environment is affected if Yokogawa B/M9000 VP r6.01.01-r6.03.02 or CENTUM VP r4.01.00-r4.03.00 is installed with accessible Graphic Builder functionality.

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

Restrict physical and logical access to systems running affected CENTUM VP versions; contact Yokogawa for patched versions or vendor guidance on securing Graphic Builder file handling.

Recommended fix Moderate confidence

B/M9000 VP: upgrade to r6.03.03 or later | Centum VP: upgrade to r4.03.01 or later (consult Yokogawa for exact fixed version)

  1. Check the official Yokogawa security advisory at www.yokogawa.com or JVN (jvn.jp) for the specific fixed version numbers and patch availability.
  2. For B/M9000 VP: Upgrade from versions r6.01.01 through r6.03.02 to the latest available version (r6.03.03 or later) that includes the security fix.
  3. For Centum VP (including Small and Basic variants): Upgrade from versions r4.01.00 through r4.03.00 to the latest available version (r4.03.01 or later) that includes the security fix.
  4. Verify the upgrade in a test environment before deploying to production.
  5. After upgrading, ensure that access controls are in place since the advisory notes the attacker needs local access to the computer where the product is installed.
Caveat Review Yokogawa release notes for any compatibility changes or deprecated features between your current version and the target upgrade version

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

Fix this in B\/m9000 Vp Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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