dbcve.org
Centum Cs 3000 FirmwareOperating system · Yokogawa

CVE-2022-21177

HIGH · 8.1 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 →
87/100
Remediation priority · High
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
There is a path traversal vulnerability in CAMS for HIS Log Server contained in the following Yokogawa Electric products: 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, andfrom 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

A path traversal vulnerability exists in the CAMS for HIS Log Server component of Yokogawa's CENTUM CS 3000, CENTUM VP, and Exaopc products. The vulnerability allows attackers to manipulate file path inputs using '..' sequences to access files outside the intended directory boundaries, potentially leading to unauthorized file access or disclosure of sensitive system files.

MitigationApply vendor-provided patches or updates when available. If no patch exists, implement input validation and filtering for path traversal sequences, and restrict the application process permissions to minimize file system exposure.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 product: CENTUM CS 3000, CENTUM VP, or Exaopc. Consult the system inventory or check the product information via the control system management interface.
    Affected if The product is one of the three affected: CENTUM CS 3000, CENTUM VP, or Exaopc.
  2. Determine firmware version
    Check the firmware version of the installed Yokogawa product. For CENTUM CS 3000, look for versions between r3.08.10 and r3.09.00 inclusive. For CENTUM VP, look for versions r4.01.00-r4.03.00, r5.01.00-r5.04.20, or r6.01.00 up to but not including r6.09.00. For Exaopc, look for versions r3.72.00 up to but not including r3.80.00.
    Affected if The installed firmware version falls within any of the affected version ranges.
  3. Confirm CAMS for HIS Log Server component
    Verify whether the CAMS for HIS Log Server component is installed and running on the system. Check the component list or running services related to CAMS (Computer-Aided Manufacturing System) and HIS (Human Interface Station) Log Server.
    Affected if The CAMS for HIS Log Server component is present and active on the system.
  4. Review access controls on log server
    Examine the configuration and permissions of the CAMS for HIS Log Server to determine if it allows file path inputs. Check for any publicly accessible endpoints or interfaces that accept file path parameters.
    Affected if The log server component accepts user-supplied file path inputs without proper validation.

The environment is affected if a Yokogawa CENTUM CS 3000, CENTUM VP, or Exaopc product with a firmware version in the listed ranges has the CAMS for HIS Log Server component installed and 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches or updates when available. If no patch exists, implement input validation and filtering for path traversal sequences, and restrict the application process permissions to minimize file system exposure.

Recommended fix Moderate confidence

CENTUM VP: R6.09.00 or later; Exaopc: R3.80.00 or later; CENTUM CS 3000: Contact Yokogawa for specific patched version

  1. 1. Identify the specific Yokogawa product and current firmware version in use (CENTUM CS 3000, CENTUM VP, or Exaopc)
  2. 2. For CENTUM VP: Upgrade firmware to version R6.09.00 or later
  3. 3. For Exaopc: Upgrade to version R3.80.00 or later
  4. 4. For CENTUM CS 3000: Contact Yokogawa directly for patched firmware version as the affected range R3.08.10-R3.09.00 may have limited support
  5. 5. After upgrade, verify the CAMS for HIS Log Server path traversal vulnerability is resolved by reviewing release notes or consulting Yokogawa documentation
Caveat Upgrade may require system downtime; verify compatibility with existing configurations and consult Yokogawa support

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-21177 — 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-21177 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