CVE-2022-22145
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 · uneditedCAMS for HIS Log Server contained in the following Yokogawa Electric products is vulnerable to uncontrolled resource consumption. 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, 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 confidenceCAMS for HIS Log Server in Yokogawa CENTUM CS 3000, CENTUM VP, and Exaopc products has an uncontrolled resource consumption vulnerability that could allow an attacker to cause a denial of service by exhausting system resources.
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>= r3.08.10, <= r3.09.00>= r3.08.10, <= r3.09.00>= r4.01.00, <= r4.03.00>= r5.01.00, <= r5.04.20>= r6.01.00, < r6.09.00>= r4.01.00, <= r4.03.00>= r5.01.00, <= r5.04.20>= r6.01.00, < r6.09.00>= r3.72.00, < r3.80.00CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Yokogawa product runningLocate the product name and model in the system documentation, HMI interface, or control system inventory. The vulnerability affects CENTUM CS 3000, CENTUM VP, and Exaopc products.Affected if The system is running any of these three product lines.
-
Check the firmware versionAccess the control system firmware or software version information through the system maintenance interface, console, or product documentation. Look for a version string in the format rX.XX.XX.Affected if The firmware version matches one of the affected ranges: r3.08.10 to r3.09.00 (CS 3000), r4.01.00 to r4.03.00, r5.01.00 to r5.04.20, or r6.01.00 to r6.08.xx (VP), or r3.72.00 to r3.79.xx (Exaopc).
-
Verify CAMS for HIS Log Server is presentCheck if the CAMS for HIS Log Server component is installed on the system. This is typically found in the software component list, installed programs, or system services related to Yokogawa's CAMS (Computer Aided Manufacturing System) historian functionality.Affected if The CAMS for HIS Log Server component is installed and running.
-
Check for unusual resource consumptionMonitor system resources such as CPU, memory, and network connections on the host running the Log Server. Look for abnormally high resource usage or connection attempts that could indicate exploitation.Affected if The system shows signs of resource exhaustion without an otherwise explainable cause.
A user is affected if they are running any of the specified product firmware versions AND have the CAMS for HIS Log Server component enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-provided patches or updates to the affected CAMS for HIS Log Server component; if patches unavailable, implement network segmentation and monitoring to mitigate exploitation.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2022-22145 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-22145 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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