B\/m9000 VpApplication · Yokogawa

CVE-2022-26034

CRITICAL · 9.1 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 →
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
Improper authentication vulnerability in the communication protocol provided by AD (Automation Design) server of CENTUM VP R6.01.10 to R6.09.00, CENTUM VP Small R6.01.10 to R6.09.00, CENTUM VP Basic R6.01.10 to R6.09.00, and B/M9000 VP R8.01.01 to R8.03.01 allows an attacker to use the functions provided by AD server. This may lead to leakage or tampering of data managed by AD server.

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 confidence

Improper authentication vulnerability in the AD (Automation Design) server communication protocol allows unauthenticated attackers to invoke AD server functions, potentially leading to unauthorized data leakage or tampering in Yokogawa CENTUM VP distributed control systems.

MitigationApply vendor-provided patches to upgrade to fixed versions of CENTUM VP and B/M9000 VP; implement network segmentation to restrict access to AD server interfaces.

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:>= r8.01.01, <= r8.03.01
Centum VpApplication
Affected:>= r6.01.10, <= r6.09.00>= r6.01.10, <= r06.09.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
None

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

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 version
    Locate the CENTUM VP or B/M9000 VP installation and retrieve the version information using the Yokogawa system information utility or check the product About/Version panel in the control system interface
    Affected if The installed version falls within >= r8.01.01 and <= r8.03.01 for B/m9000 VP, or >= r6.01.10 and <= r6.09.00 for CENTUM VP
  2. Confirm AD server functionality is enabled
    Check the AD server configuration settings within the Yokogawa control system environment to determine if the Automation Design server communication protocol is active
    Affected if The AD server interface or protocol is configured and running in the environment
  3. Verify network accessibility of AD server ports
    Scan network listening ports or check firewall rules to determine if the AD server communication ports are exposed to network access
    Affected if AD server ports are reachable from network segments other than trusted control system networks
  4. Check for unauthenticated AD server access
    Attempt to query or access the AD server interface without credentials to verify if authentication is being enforced (only perform this in authorized test environments)
    Affected if AD server functions can be invoked without providing valid authentication credentials

You are affected if the installed Yokogawa CENTUM VP or B/M9000 VP version falls within the affected ranges AND the AD server protocol is enabled and accessible on the network without authentication.

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-provided patches to upgrade to fixed versions of CENTUM VP and B/M9000 VP; implement network segmentation to restrict access to AD server interfaces.

Fix this in B\/m9000 Vp Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26034 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