dbcve.org
Centum Cs 3000 FirmwareOperating system · Yokogawa

CVE-2020-5609

CRITICAL · 9.8 CVSS v3.1 Published 2020-08-05
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
Directory traversal vulnerability in CAMS for HIS CENTUM CS 3000 (includes CENTUM CS 3000 Small) R3.08.10 to R3.09.50, CENTUM VP (includes CENTUM VP Small, Basic) R4.01.00 to R6.07.00, B/M9000CS R5.04.01 to R5.05.01, and B/M9000 VP R6.01.01 to R8.03.01 allows a remote unauthenticated attacker to create or overwrite arbitrary files and run arbitrary commands via unspecified vectors.

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

Directory traversal vulnerability in Yokogawa's CAMS for HIS (Hospital Information System) industrial control software allows remote unauthenticated attackers to navigate file system paths and create/overwrite arbitrary files, leading to arbitrary command execution. The flaw affects CENTUM CS 3000, CENTUM VP, B/M9000CS, and B/M9000 VP control system platforms across multiple version ranges.

MitigationApply vendor-provided patches to upgrade to fixed versions of the affected products. Until patched, isolate affected systems on separate network segments, restrict access to authorized personnel only, and monitor for indicators of compromise.

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.50
Centum Vp FirmwareOperating system
Affected:>= r4.01.00, <= r4.03.00>= r5.01.00, <= r5.04.20>= r6.01.00, <= r6.07.00
B\/m9000cs FirmwareOperating system
Affected:>= r5.04.01, <= r5.05.01
B\/m9000vp FirmwareOperating system
Affected:>= r6.01.01, <= r8.03.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
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 if Yokogawa CAMS for HIS component is installed
    Locate and inspect the CAMS for HIS web application component on the system. Check for the presence of CAMS for HIS directories and configuration files typically found in the Yokogawa installation path.
    Affected if The CAMS for HIS web application component is present and running on the system.
  2. Determine the installed firmware version of the Yokogawa control system
    Access the control system console or management interface and retrieve the firmware version information. For CENTUM CS 3000, CENTUM VP, B/M9000CS, or B/M9000 VP platforms, check the system information or version display function.
    Affected if The installed firmware version falls within any of the following ranges: CENTUM CS 3000 r3.08.10 through r3.09.50; CENTUM VP r4.01.00 through r4.03.00, r5.01.00 through r5.04.20, or r6.01.00 through r6.07.00; B/M9000CS r5.04.01 through r5.05.01; B/M9000VP r6.01.01 through r8.03.01.
  3. Verify if CAMS for HIS web interface is network accessible
    Check network configuration and firewall rules to determine if the CAMS for HIS web service port is exposed to network access. Identify the listening port used by the CAMS for HIS HTTP service.
    Affected if The CAMS for HIS web interface is accessible from network segments outside the isolated control system environment.
  4. Inspect for unauthorized files or modifications in the web application directory
    Examine the CAMS for HIS web root directory and associated file system locations for unexpected files, particularly script files or executables that were not originally installed as part of the CAMS for HIS package.
    Affected if Unexpected files appear in the CAMS for HIS directories, especially in locations that would be reachable through the directory traversal vulnerability.

A system is affected if it runs any of the listed Yokogawa control system platforms with firmware versions within the affected ranges and has the CAMS for HIS component installed and 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 to upgrade to fixed versions of the affected products. Until patched, isolate affected systems on separate network segments, restrict access to authorized personnel only, and monitor for indicators of compromise.

Fix this in Centum Cs 3000 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation16.0 h
  • Testing20.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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