dbcve.org
Centum Cs 3000 FirmwareOperating system · Yokogawa

CVE-2022-22141

HIGH · 7.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 →
80/100
Remediation priority · High
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
'Long-term Data Archive Package' service implemented in the following Yokogawa Electric products creates some named pipe with imporper ACL configuration. 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, 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

The 'Long-term Data Archive Package' service in Yokogawa CENTUM CS 3000, CENTUM VP, and Exaopc creates Windows named pipes with improperly configured Access Control Lists (ACLs). This misconfiguration allows local unprivileged users to potentially interact with or impersonate the service account via the named pipe, leading to local privilege escalation.

MitigationApply vendor-supplied patches or upgrade to a non-vulnerable version of the affected software. If patches are unavailable, restrict local user access to the affected systems and monitor for suspicious pipe interactions.

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

CVSS:3.1/AV:L/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 the Long-term Data Archive Package service
    Open Windows Services console (services.msc) or run 'Get-Service' in PowerShell and search for a service related to 'Long-term Data Archive', 'Data Archive', or 'LTDA' or 'Yokogawa Archive'
    Affected if The service exists and is running on the system
  2. Determine installed product version
    Check the version of Yokogawa CENTUM CS 3000, CENTUM VP, or Exaopc installed. This is typically available in the software's About/Version dialog, in the Windows Programs and Features list, or in the installation directory. For firmware versions, consult the system control system information.
    Affected if The installed version falls within any of these ranges: CENTUM CS 3000 r3.08.10 to r3.09.00; CENTUM VP r4.01.00-r4.03.00, r5.01.00-r5.04.20, or r6.01.00-r6.08.99; Exaopc r3.72.00-r3.79.99
  3. Inspect named pipe ACLs
    Use PowerShell with the Sysinternals tool 'pspipe' or the 'Get-Acl' cmdlet to list named pipes on the system. Look for pipes that may be created by the archive service. Use 'pipeacl' or similar tools to examine the security descriptor on any archive-related named pipes.
    Affected if Any named pipe associated with the Long-term Data Archive Package service grants excessive permissions to the Everyone group or allows non-privileged users to have write or impersonate access
  4. Check for local user privileges
    Run 'whoami /all' or check Local Users and Groups (lusrmgr.msc) to see what local users exist on the system. The vulnerability allows unprivileged local users to potentially interact with or impersonate the service account.
    Affected if There are non-administrator local user accounts on the system and the named pipe ACLs permit their access

Your environment is affected if the Long-term Data Archive Package service is running, the installed version is within the affected ranges listed above, AND the named pipes created by this service have overly permissive ACLs allowing unprivileged access.

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-supplied patches or upgrade to a non-vulnerable version of the affected software. If patches are unavailable, restrict local user access to the affected systems and monitor for suspicious pipe interactions.

Fix this in Centum Cs 3000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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