dbcve.org
AnalytixApplication · Iconics

CVE-2022-23128

CRITICAL · 9.8 CVSS v3.1 Published 2022-01-21
Fix available
A fix is available. Upgrade to after 10.97 or later.
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
Incomplete List of Disallowed Inputs vulnerability in Mitsubishi Electric MC Works64 versions 4.00A (10.95.201.23) to 4.04E (10.95.210.01), ICONICS GENESIS64 versions 10.95.3 to 10.97, ICONICS Hyper Historian versions 10.95.3 to 10.97, ICONICS AnalytiX versions 10.95.3 to 10.97 and ICONICS MobileHMI versions 10.95.3 to 10.97 allows a remote unauthenticated attacker to bypass the authentication of MC Works64, GENESIS64, Hyper Historian, AnalytiX and MobileHMI, and gain unauthorized access to the products, by sending specially crafted WebSocket packets to FrameWorX server, one of the functions of the products.

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

Incomplete input validation in the FrameWorX server's WebSocket handling allows remote unauthenticated attackers to bypass authentication mechanisms by sending specially crafted WebSocket packets. This affects multiple ICONICS-based products used in industrial control environments.

MitigationApply vendor-supplied patches to affected products (MC Works64 4.04F or later, GENESIS64 10.97.1 or later). If patches unavailable, restrict network access to FrameWorX server ports and implement WAF rules to validate WebSocket traffic.

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
AnalytixApplication
Affected:>= 10.95.3, <= 10.97
Genesis64Application
Affected:>= 10.95.3, <= 10.97
Hyper HistorianApplication
Affected:>= 10.95.3, <= 10.97
MobilehmiApplication
Affected:>= 10.95.3, <= 10.97
Mc Works64Application
Affected:>= 10.95.201.23, <= 10.95.210.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 installed ICONICS-based products
    Review installed software on the system for any of these product names: Analytix, Genesis64, Hyper Historian, MobileHMI, or Mc Works64. Check Windows Programs and Features, installation directories, or industrial control system asset inventories.
    Affected if Any of these products are present on the system
  2. Determine installed product version
    Locate the version information for the identified product. Check product About dialogs, version info in executable file properties, or product-specific configuration files. For Mc Works64, check the installed version in Windows Programs and Features.
    Affected if The installed version falls within the affected ranges: Analytix/G genesis64/Hyper Historian/MobileHMI versions 10.95.3 through 10.97, or Mc Works64 versions 10.95.201.23 through 10.95.210.01
  3. Verify FrameWorX server component is in use
    Check if the FrameWorX server service or component is running. Look for processes named FrameWorX, check for open ports associated with FrameWorX (typically WebSocket ports), or review product documentation to confirm FrameWorX is enabled.
    Affected if FrameWorX server is installed and active
  4. Confirm WebSocket handling is enabled
    Review product configuration settings or service definitions to determine if WebSocket communication is enabled. Check FrameWorX server configuration files or management interfaces for WebSocket listener status.
    Affected if WebSocket handling feature is enabled in the product configuration
  5. Review network exposure of FrameWorX services
    Examine firewall rules, network configurations, or port bindings to determine if FrameWorX server ports are accessible from network segments beyond the local machine or trusted zones.
    Affected if FrameWorX WebSocket ports are exposed to untrusted networks

A system is affected if it runs any of the listed ICONICS products (Analytix, Genesis64, Hyper Historian, MobileHMI, or Mc Works64) within the specified version ranges AND has FrameWorX server with WebSocket handling enabled and exposed.

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
Upgrade available Upgrade to a release after 10.97
Interim mitigation

Apply vendor-supplied patches to affected products (MC Works64 4.04F or later, GENESIS64 10.97.1 or later). If patches unavailable, restrict network access to FrameWorX server ports and implement WAF rules to validate WebSocket traffic.

Fix this in Analytix Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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