dbcve.org
Centum Cs 3000 FirmwareOperating system · Yokogawa

CVE-2022-30707

HIGH · 8.8 CVSS v3.1 Published 2022-06-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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
Violation of secure design principles exists in the communication of CAMS for HIS. Affected products and versions are CENTUM series where LHS4800 is installed (CENTUM CS 3000 and CENTUM CS 3000 Small R3.08.10 to R3.09.00), CENTUM series where CAMS function is used (CENTUM VP, CENTUM VP Small, and CENTUM VP Basic R4.01.00 to R4.03.00), CENTUM series regardless of the use of CAMS function (CENTUM VP, CENTUM VP Small, and CENTUM VP Basic R5.01.00 to R5.04.20 and R6.01.00 to R6.09.00), Exaopc R3.72.00 to R3.80.00 (only if NTPF100-S6 'For CENTUM VP Support CAMS for HIS' is installed), B/M9000 CS R5.04.01 to R5.05.01, and B/M9000 VP R6.01.01 to R8.03.01). If an adjacent attacker successfully compromises a computer using CAMS for HIS software, they can use credentials from the compromised machine to access data from another machine using CAMS for HIS software. This can lead to a disabling of CAMS for HIS software functions on any affected machines, or information disclosure/alteration.

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

This vulnerability in Yokogawa CAMS for HIS involves a secure design flaw in inter-machine communication. An attacker who has compromised one CAMS for HIS workstation can harvest credentials and use them to authenticate to other CAMS for HIS systems on the same network segment, enabling unauthorized data access, function disruption, and potential information manipulation.

MitigationApply vendor-provided patches for affected versions; implement network segmentation to isolate CAMS for HIS systems and enforce strict access controls between workstations.

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 Class 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 Class 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
B\/m9000 VpApplication
Affected:>= r6.01.01, <= r8.03.01
B\/m9000csApplication
Affected:>= r5.04.01, <= r5.05.01

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 installed Yokogawa product and firmware version
    Locate the CAMS for HIS application or check the firmware version on the Yokogawa system. This is typically accessible through the system console, control system management interface, or product documentation. Record the exact firmware version string (for example, r3.08.10, r5.04.20, v8.03.01).
    Affected if The firmware version matches any of the following ranges: Centum CS 3000 or Entry Class (r3.08.10 through r3.09.00); Centum VP or Entry Class (r4.01.00 through r4.03.00, r5.01.00 through r5.04.20, or r6.01.00 through r6.09.00); Exaopc (r3.72.00 through r3.80.00); B/m9000 VP (r6.01.01 through v8.03.0
  2. Confirm CAMS for HIS inter-machine communication is configured
    Review the CAMS for HIS configuration settings to determine if communication between multiple workstations is enabled. This typically involves checking the system's network configuration, communication settings, or inter-station messaging parameters within the CAMS for HIS management console.
    Affected if Inter-machine communication or workstation-to-workstation messaging features are enabled on the system.
  3. Determine if multiple CAMS for HIS systems exist on the same network segment
    Audit the network environment to identify all CAMS for HIS workstations. Use network scanning, review network topology documentation, or query the control system network configuration to enumerate all connected CAMS for HIS nodes.
    Affected if Two or more CAMS for HIS workstations are present on the same local network segment or subnet.
  4. Verify credential storage and transmission settings
    Inspect the CAMS for HIS security configuration to determine how user credentials are stored and transmitted between workstations. Look for settings related to credential caching, authentication token handling, or inter-station credential sharing.
    Affected if Credentials are stored in a manner that permits retrieval by other CAMS for HIS workstations on the network, or if inter-station authentication uses shared secret material.

A system is affected if it runs a Yokogawa CAMS for HIS firmware version within the affected ranges AND has inter-machine communication enabled with other CAMS for HIS workstations on the same network segment.

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 for affected versions; implement network segmentation to isolate CAMS for HIS systems and enforce strict access controls between workstations.

Recommended fix Moderate confidence

Contact Yokogawa for specific fixed versions beyond the affected ranges (e.g., beyond r3.09.00, r4.03.00, r5.04.20, r6.09.00, r3.80.00, r8.03.01, r5.05.01)

  1. Contact Yokogawa technical support to obtain the specific firmware updates that address CVE-2022-30707
  2. Request the latest fixed firmware version for your specific product line (CENTUM CS 3000, CENTUM VP, Exaopc, B/M9000 VP, or B/M9000 CS)
  3. Verify the fixed version with Yokogawa before upgrading to ensure it addresses the CAMS for HIS credential reuse vulnerability
  4. Schedule a maintenance window for the firmware upgrade following Yokogawa's recommended upgrade procedure
  5. After upgrading, verify that the CAMS for HIS communication now properly authenticates each connection independently
  6. Implement network segmentation to isolate CAMS for HIS workstations as an additional defense-in-depth measure
Caveat Firmware upgrades on industrial control systems may require extensive testing in a non-production environment and could affect integration with connected control system components; coordinate with Yokogawa and plant operations

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 / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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