dbcve.org
Centum Cs 3000 Cp401 FirmwareOperating system · Yokogawa

CVE-2022-33939

HIGH · 7.5 CVSS v3.1 Published 2022-08-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
CENTUM VP / CS 3000 controller FCS (CP31, CP33, CP345, CP401, and CP451) contains an issue in processing communication packets, which may lead to resource consumption. If this vulnerability is exploited, an attacker may cause a denial of service (DoS) condition in ADL communication by sending a specially crafted packet to the affected product.

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 vulnerability exists in the ADL communication packet processing of specific Honeywell/Flowserve CENTUM VP/CS 3000 controller models (CP31, CP33, CP345, CP401, CP451). Processing of specially crafted packets leads to resource consumption, causing a denial of service condition in ADL communication. This is an ICS/OT vulnerability affecting industrial control system network communications.

MitigationApply vendor patches when available; until then, implement network segmentation to isolate affected controllers from untrusted networks and monitor for anomalous ADL communication patterns indicating exploitation attempts.

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 Cp401 FirmwareOperating system
Affected:all versions
Centum Cs 3000 Cp451 FirmwareOperating system
Affected:all versions
Centum Cs 3000 Cp33 FirmwareOperating system
Affected:all versions
Centum Cs 3000 Cp345 FirmwareOperating system
Affected:all versions
Centum Cs 3000 Cp31 FirmwareOperating system
Affected:all versions
Centum Vp 3000 Cp401 FirmwareOperating system
Affected:>= r4.01.00, <= r4.03.00>= r5.01.00, < r5.04.78>= r6.01.00, < r6.03.10
Centum Vp 3000 Cp451 FirmwareOperating system
Affected:>= r4.01.00, <= r4.03.00>= r5.01.00, < r5.04.78>= r6.01.00, < r6.03.10

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 controller model
    Access the controller via its console, engineering station software, or system documentation to determine the exact CP model number (CP31, CP33, CP345, CP401, or CP451)
    Affected if The controller model is one of: CP31, CP33, CP345, CP401, or CP451
  2. Determine firmware version
    Check the controller firmware version through its built-in web interface, serial console, or engineering station diagnostics. Look for version strings such as r4.xx.xx, r5.xx.xx, or r6.xx.xx
    Affected if For Centum CS 3000: any version. For Centum VP 3000 CP401/CP451: version r4.01.00 through r4.03.00, r5.01.00 through r5.04.77, or r6.01.00 through r6.03.09
  3. Verify ADL communication is active
    Check controller network configuration and ADL protocol settings via the engineering station or controller console. Confirm ADL communication interfaces are enabled and configured
    Affected if ADL communication protocol is enabled and the controller is actively communicating over ADL-enabled network interfaces
  4. Assess network exposure
    Review network segmentation and firewall rules to determine if the controller network (where ADL communication occurs) is accessible from less trusted networks or the corporate IT network
    Affected if The controller's ADL communication network is reachable from untrusted or less-trusted network segments without proper isolation

You are affected if you operate any Centum CS 3000 or VP 3000 controller model CP31/CP33/CP345/CP401/CP451 with ADL communication enabled and your firmware version falls within the affected ranges, especially if the controller network is exposed to untrusted segments.

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 patches when available; until then, implement network segmentation to isolate affected controllers from untrusted networks and monitor for anomalous ADL communication patterns indicating exploitation attempts.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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