dbcve.org
Centum Vp FirmwareOperating system · Yokogawa

CVE-2022-23402

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 hard-code the password for CAMS server applications: CENTUM VP versions from R5.01.00 to R5.04.20 and versions 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 · high confidence

Yokogawa CENTUM VP and Exaopc products contain hard-coded passwords embedded in the CAMS server application code. This allows attackers to bypass authentication and gain unauthorized access to these industrial control system components. The hard-coded credentials cannot be changed by administrators, making exploitation straightforward and reliable.

MitigationApply vendor-provided patches to update to patched versions of CENTUM VP and Exaopc. Until patches are applied, isolate affected systems behind network firewalls and restrict access to trusted personnel only.

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:>= 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 CENTUM VP installation and version
    Locate the CENTUM VP installation directory or check system registry for firmware version information. Look for version files, commonly found in the installation path under version or system directories.
    Affected if The installed firmware version is r5.01.00 through r5.04.20, or r6.01.00 through r6.08.x (any version below r6.09.00)
  2. Identify CENTUM VP Entry installation and version
    Locate the CENTUM VP Entry installation and retrieve its firmware version from version files or system information, similar to CENTUM VP.
    Affected if The installed firmware version is r5.01.00 through r5.04.20, or r6.01.00 through r6.08.x (any version below r6.09.00)
  3. Identify Exaopc installation and version
    Locate the Exaopc installation directory and retrieve the version from version files or application information, typically found in the installation path.
    Affected if The installed version is r3.72.00 through r3.79.x (any version below r3.80.00)
  4. Verify CAMS server component is present
    Check for the presence of the CAMS server application within the CENTUM VP or Exaopc installation. Look for cams.exe, camsserver, or similar CAMS-related processes or services.
    Affected if The CAMS server component is installed and running as part of the affected product installation

You are affected if any Yokogawa CENTUM VP, CENTUM VP Entry, or Exaopc installation with an active CAMS server component has a version falling within the affected ranges: r5.01.00-r5.04.20, r6.01.00-r6.08.x, or r3.72.00-r3.79.x.

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-provided patches to update to patched versions of CENTUM VP and Exaopc. Until patches are applied, isolate affected systems behind network firewalls and restrict access to trusted personnel only.

Recommended fix High confidence

CENTUM VP: R6.09.00 or later; Exaopc: R3.80.00 or later

  1. 1. Identify the exact installed version of CENTUM VP or Exaopc in your environment
  2. 2. If running CENTUM VP firmware version R5.01.00 to R5.04.20, upgrade to R6.09.00 or later
  3. 3. If running CENTUM VP firmware version R6.01.00 to R6.08.00, upgrade to R6.09.00 or later
  4. 4. If running Exaopc version R3.72.00 to R3.79.00, upgrade to R3.80.00 or later
  5. 5. After upgrade, verify that default credentials have been changed according to vendor documentation
  6. 6. Review and rotate any credentials that may have been using the hard-coded values
Caveat Upgrading major versions may require migration planning; consult Yokogawa upgrade documentation for compatibility with existing configurations

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

Fix this in Centum Vp Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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