dbcve.org
Centum Cs 3000 FirmwareOperating system · Yokogawa

CVE-2022-23401

HIGH · 7.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 →
81/100
Remediation priority · High
No privileges

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 contain insecure DLL loading issues. CENTUM CS 3000 versions from R3.08.10 to R3.09.00, CENTUM VP versions from R4.01.00 to R4.03.00, from R5.01.00 to R5.04.20, and from R6.01.00 to R6.08.00, 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 · moderate confidence

Insecure DLL loading vulnerability in Yokogawa CENTUM CS 3000, CENTUM VP, and Exaopc allows attackers to execute arbitrary code by placing malicious DLLs in locations from which the applications load DLLs, potentially achieving code execution with the application's privileges.

MitigationApply vendor patches when available; until then, restrict file system permissions on directories used by these applications and ensure only trusted binaries exist in DLL search paths.

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.08.10, <= r3.09.00
Centum Cs 3000 Entry FirmwareOperating system
Affected:>= r3.08.10, <= r3.09.00
Centum Vp FirmwareOperating system
Affected:>= r4.01.00, <= r4.03.00>= 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 products
    Locate Yokogawa CENTUM CS 3000, CENTUM VP, or Exaopc installations on the system. Check common installation directories such as C:\Yokogawa or C:\Program Files\Yokogawa, and review installed programs list.
    Affected if Any of these three products are installed on the system
  2. Determine CENTUM CS 3000 firmware version
    Access the control system engineering station and retrieve the firmware version from the system information or about section. Look for a version string in the format r3.08.10 through r3.09.00.
    Affected if Firmware version is >= r3.08.10 and <= r3.09.00 for either standard or Entry firmware
  3. Determine CENTUM VP firmware version
    Access the control system engineering station and retrieve the firmware version from the system information or about section. Check for versions in ranges r4.01.00-r4.03.00, r5.01.00-r5.04.20, or r6.01.00-r6.09.00 (excluding r6.09.00 and above).
    Affected if Firmware version is >= r4.01.00 and <= r4.03.00, OR >= r5.01.00 and <= r5.04.20, OR >= r6.01.00 and < r6.09.00 for either standard or Entry firmware
  4. Determine Exaopc version
    Locate the Exaopc installation directory and check the version information in the application properties or readme files. Look for version strings between r3.72.00 and r3.80.00.
    Affected if Exaopc version is >= r3.72.00 and < r3.80.00
  5. Review DLL search paths for suspicious files
    Examine directories in the application DLL search path (typically the installation folder and subdirectories) for unauthorized or unexpected DLL files that may have been placed by an attacker.
    Affected if Unexpected DLL files exist in the application installation directories and the product version falls within the affected ranges

The environment is affected if any of these Yokogawa products are installed and their version falls within the specified affected ranges, and unauthorized DLLs could be placed in the application's DLL search path.

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

Apply vendor patches when available; until then, restrict file system permissions on directories used by these applications and ensure only trusted binaries exist in DLL search paths.

Recommended fix High confidence

CENTUM VP: upgrade to r6.09.00 or later; Exaopc: upgrade to r3.80.00 or later; CENTUM CS 3000: upgrade to a version above r3.09.00 (consult Yokogawa for specific path)

  1. Identify the specific product (CENTUM CS 3000, CENTUM VP, or Exaopc) and current firmware version in use
  2. Consult Yokogawa's official documentation at web-material3.yokogawa.com to obtain the upgrade package for your product
  3. Download the firmware upgrade from Yokogawa's official support portal
  4. Follow Yokogawa's standard firmware upgrade procedure for the respective product (this typically requires stopping the process, applying the upgrade, and restarting)
  5. After upgrade, verify the DLL loading behavior by checking that the application only loads DLLs from trusted, controlled directories
  6. Confirm the new version matches or exceeds the fixed release (r6.09.00 for CENTUM VP, r3.80.00 for Exaopc, or a version above r3.09.00 for CENTUM CS 3000)
Caveat None explicitly documented; follow standard Yokogawa firmware upgrade procedures

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

Fix this in Centum Cs 3000 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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