dbcve.org
B\/m9000 VpApplication · Yokogawa

CVE-2023-26593

HIGH · 7.8 CVSS v3.1 Published 2023-04-11
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
CENTUM series provided by Yokogawa Electric Corporation are vulnerable to cleartext storage of sensitive information. If an attacker who can login or access the computer where the affected product is installed tampers the password file stored in the computer, the user privilege which CENTUM managed may be escalated. As a result, the control system may be operated with the escalated user privilege. To exploit this vulnerability, the following prerequisites must be met: (1)An attacker has obtained user credentials where the affected product is installed, (2)CENTUM Authentication Mode is used for user authentication when CENTUM VP is used. The affected products and versions are as follows: CENTUM CS 1000, CENTUM CS 3000 (Including CENTUM CS 3000 Entry Class) R2.01.00 to R3.09.50, CENTUM VP (Including CENTUM VP Entry Class) R4.01.00 to R4.03.00, R5.01.00 to R5.04.20, and R6.01.00 and later, B/M9000 CS R5.04.01 to R5.05.01, and B/M9000 VP R6.01.01 to R7.04.51 and R8.01.01 and later

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

The vulnerability involves cleartext storage of sensitive authentication information (passwords) in password files within Yokogawa CENTUM control systems. An attacker with valid user credentials who gains access to the computer can tamper with these password files to escalate privileges, allowing unauthorized operation of the control system with elevated user rights.

MitigationOrganizations should upgrade to vendor-provided patched versions where available, or implement proper password hashing/encryption mechanisms. Until patched, minimize local access to systems using CENTUM Authentication Mode and monitor for unauthorized modifications to password files.

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, <= r7.04.51>= r8.01.01
B\/m9000csApplication
Affected:>= r5.04.01, <= r5.05.01
Centum Cs 1000Application
Affected:>= r2.01.00, <= r3.09.50
Centum Cs 3000Application
Affected:>= r2.01.00, <= r3.09.50
Centum Cs 3000 Entry ClassApplication
Affected:>= r2.01.00, <= r3.09.50
Centum VpApplication
Affected:>= r4.01.00, <= r4.03.00>= r5.01.00, <= r5.04.20>= r6.01.00
Centum Vp Entry ClassApplication
Affected:>= r4.01.00, <= r4.02.00>= r5.01.00, <= r5.04.20>= r6.01.00
ExaopcApplication
Affected:>= r1.01.00, <= r1.20.00>= r2.01.00, <= r2.10.00>= r3.01.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 product and version
    Locate the Yokogawa CENTUM software installation and determine the exact version number (for example, check the About or version information in the control system software, or look for version metadata in the installation directory)
    Affected if The installed version falls within any of the affected ranges: B/m9000 Vp (r6.01.01-r7.04.51 or r8.01.01+), B/m9000cs (r5.04.01-r5.05.01), Centum Cs 1000 (r2.01.00-r3.09.50), Centum Cs 3000 (r2.01.00-r3.09.50), Centum Cs 3000 Entry Class (r2.01.00-r3.09.50), Centum Vp (r4.01.00-r4.03.00, r5.01.00-r5
  2. Locate password files
    Find the password or user credential files used by the CENTUM authentication system (consult system documentation for default locations or search for files containing user/password data within the installation directory)
    Affected if Password files exist on the system and are accessible to local users
  3. Inspect password file contents
    Open or parse the password files and examine whether passwords are stored in cleartext (readable text) rather than being hashed or encrypted
    Affected if Passwords are stored in plaintext or recoverable cleartext format within the files
  4. Check authentication mode configuration
    Determine if the system is configured to use CENTUM Authentication Mode (this may be visible in system settings, registry, or configuration files)
    Affected if CENTUM Authentication Mode is enabled and relies on the vulnerable password file storage mechanism
  5. Verify file permissions on password storage
    Examine the access permissions on the password files to determine if standard users can read or modify them
    Affected if Non-privileged users have read or write access to the password files

You are affected if your installed product version falls within the affected version ranges AND password files contain cleartext authentication credentials that can be accessed or modified by local users.

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

Organizations should upgrade to vendor-provided patched versions where available, or implement proper password hashing/encryption mechanisms. Until patched, minimize local access to systems using CENTUM Authentication Mode and monitor for unauthorized modifications to password files.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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