dbcve.org
Centum Cs 3000 FirmwareOperating system · Yokogawa

CVE-2022-22729

HIGH · 8.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 →
94/100
Remediation priority · Urgent
Remotely reachable 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
CAMS for HIS Server contained in the following Yokogawa Electric products improperly authenticate the receiving packets. The authentication may be bypassed via some crafted packets: 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, and 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

CAMS for HIS Server in Yokogawa CENTUM CS 3000, CENTUM VP, and Exaopc has improper authentication validation for incoming packets. Attackers can bypass the authentication mechanism by sending specially crafted packets, potentially allowing unauthorized access to the DCS environment.

MitigationApply vendor-provided patches for all affected versions. Implement network segmentation and compensating controls (e.g., firewalls, allowlists) to restrict unauthorized packet traffic until patches can be deployed.

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

CVSS:3.1/AV:N/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 Yokogawa product
    Locate and check the installed Yokogawa CENTUM product (CS 3000, CENTUM VP, or Exaopc) on the system or control system environment
    Affected if The system is running any of the affected products (CENTUM CS 3000, CENTUM VP, or Exaopc)
  2. Determine firmware version
    Access the system firmware information through the Yokogawa system management interface, console, or product documentation to retrieve the exact version number
    Affected if The installed version falls within any of these ranges: CS 3000/r3.08.10-r3.09.00, VP r4.01.00-r4.03.00 or r5.01.00-r5.04.20 or r6.01.00-<r6.09.00, Exaopc r3.72.00-<r3.80.00
  3. Verify CAMS for HIS Server presence
    Check if the CAMS (Computer Aided Manufacturing System) for HIS (Human Interface Station) Server component is installed and running on the affected system
    Affected if CAMS for HIS Server is installed and active on the target system
  4. Inspect network exposure
    Review network configuration, firewall rules, and access controls to determine if the CAMS for HIS Server is accessible from network segments outside the trusted DCS environment
    Affected if CAMS for HIS Server is exposed to untrusted network segments or has insufficient network filtering
  5. Review authentication configuration
    Examine the authentication settings and packet validation configuration for the CAMS for HIS Server through the system administration tools or configuration files
    Affected if Authentication validation for incoming packets is enabled but improperly configured or can be bypassed

The environment is affected if CAMS for HIS Server is running on a Yokogawa CENTUM CS 3000, CENTUM VP, or Exaopc system with a firmware version matching the affected ranges and the component is network-accessible.

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 for all affected versions. Implement network segmentation and compensating controls (e.g., firewalls, allowlists) to restrict unauthorized packet traffic until patches can be deployed.

Fix this in Centum Cs 3000 Firmware 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-22729 — 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-22729 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