dbcve.org
Centum Cs 3000 FirmwareOperating system · Yokogawa

CVE-2022-22151

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
CAMS for HIS Log Server contained in the following Yokogawa Electric products fails to properly neutralize log outputs: 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 · moderate confidence

CAMS for HIS Log Server in Yokogawa CENTUM CS 3000, CENTUM VP, and Exaopc fails to properly neutralize log outputs, allowing injection of malicious content into logs through unsanitized input.

MitigationImplement proper input validation and sanitization for all data being written to logs to prevent log injection attacks.

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 the Yokogawa product in use
    Check system inventory, documentation, or deployed software list to confirm whether the environment includes CENTUM CS 3000, CENTUM VP, or Exaopc products.
    Affected if The product is not one of these three (CENTUM CS 3000, CENTUM VP, or Exaopc), then it is not affected.
  2. Determine the firmware version
    Access the system control panel, firmware management interface, or run the vendor-provided version query command to retrieve the installed firmware version number.
    Affected if The installed version falls within any of these ranges: r3.08.10 to r3.09.00 (CENTUM CS 3000), r4.01.00 to r4.03.00 / r5.01.00 to r5.04.20 / r6.01.00 to <r6.09.00 (CENTUM VP), or r3.72.00 to <r3.80.00 (Exaopc).
  3. Confirm CAMS for HIS Log Server is active
    Check the running processes, services list, or application modules to verify whether the CAMS for HIS Log Server component is installed and active.
    Affected if CAMS for HIS Log Server is present and running; if this component is not installed, the vulnerability does not apply.
  4. Inspect log file locations for unsanitized content
    Locate the log directories for CAMS for HIS Log Server (typically under the Yokogawa installation logs folder) and examine recent log entries for unexpected line breaks, injected timestamps, or content that suggests malicious input was written directly to logs.
    Affected if Log files contain entries with injected content (newlines, false timestamps, or arbitrary data inserted by an attacker), indicating successful exploitation of the log injection flaw.

The environment is affected if it runs CENTUM CS 3000, CENTUM VP, or Exaopc with a firmware version within the affected ranges AND the CAMS for HIS Log Server component is installed and processing external inputs without sanitization.

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

Implement proper input validation and sanitization for all data being written to logs to prevent log injection attacks.

Recommended fix Moderate confidence

CENTUM VP: R6.09.00 or later; Exaopc: R3.80.00 or later; CENTUM CS 3000: Contact vendor

  1. 1. Identify the specific product (CENTUM CS 3000, CENTUM VP, or Exaopc) and current firmware version from the affected system
  2. 2. For CENTUM VP: Upgrade to firmware 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 Electric Corporation directly for remediation guidance, as no fixed version is specified in the available documentation
  5. 5. After upgrade, verify that CAMS for HIS Log Server is functioning correctly and log outputs are properly sanitized
  6. 6. Review system logs to confirm the vulnerability has been mitigated
Caveat Review release notes for CENTUM VP R6.09.00 and Exaopc R3.80.00 for any compatibility or configuration changes before upgrading

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

Fix this in Centum Cs 3000 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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