dbcve.org
Genesis64Application · Iconics

CVE-2022-33315

HIGH · 7.8 CVSS v3.1 Published 2022-07-20
Fix available
A fix is available. Upgrade to after 10.95.210.01 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Deserialization of Untrusted Data vulnerability in Mitsubishi Electric GENESIS64 versions 10.97 to 10.97.1, Mitsubishi Electric Iconics Digital Solutions GENESIS64 versions 10.97 to 10.97.1, Mitsubishi Electric ICONICS Suite versions 10.97 to 10.97.1, Mitsubishi Electric Iconics Digital Solutions ICONICS Suite versions 10.97 to 10.97.1, and Mitsubishi Electric MC Works64 versions 4.04E and prior allows an unauthenticated attacker to execute an arbitrary malicious code by leading a user to load a monitoring screen file including malicious XAML codes.

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

A deserialization vulnerability in Mitsubishi Electric GENESIS64 and related products (versions 10.97 to 10.97.1, MC Works64 4.04E and prior) allows unauthenticated attackers to execute arbitrary code by tricking users into loading malicious XAML monitoring screen files. The vulnerability stems from insecure deserialization of untrusted XAML data.

MitigationApply vendor-supplied patches when available; until then, enforce strict controls on loading monitoring screen files from untrusted sources, disable XAML file loading if possible, and educate users about not opening suspicious screen files.

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
Genesis64Application
Affected:= 10.97= 10.97.1
Mc Works64Application
Affected:<= 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 Genesis64 or MC Works64 is installed
    Check the Windows Programs and Features list (appwiz.cpl) or look for installation directories such as C:\Program Files\ICONICS\Genesis64 or C:\Program Files\Mitsubishi Electric\MC Works64
    Affected if Either Mitsubishi Electric GENESIS64 or MC Works64 is present on the system
  2. Determine the installed version of Genesis64
    Check the version of GENESIS64 by right-clicking the installed executable, selecting Properties, and viewing the Details tab, or check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\ICONICS\Genesis64 for the Version value
    Affected if The installed version is 10.97, 10.97.1, or falls within the range 10.97 to 10.97.1
  3. Determine the installed version of MC Works64
    Check the version of MC Works64 in Programs and Features, or check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Mitsubishi Electric\MC Works64 for the Version value
    Affected if The installed version is 10.95.210.01 or lower, or is version 4.04E or prior
  4. Check if XAML monitoring screen file loading is enabled
    Examine the application configuration files (such as .config files in the installation directory) for settings related to XAML loading, deserialization, or screen file import functionality. Look for entries like EnableXamlLoading, AllowExternalScreens, or similar configuration flags
    Affected if XAML file loading or deserialization from external sources is permitted in the configuration
  5. Inspect the XAML monitoring screen file handling configuration
    Look in the installation folder for configuration files that control how .xaml, .gxw, or other monitoring screen files are processed. Check for security-related settings in the application settings or XML configuration files
    Affected if The application is configured to load XAML monitoring screens without requiring explicit security validation or digital signature verification

A system is affected if it has Genesis64 version 10.97 through 10.97.1 or MC Works64 version 10.95.210.01 or lower (or 4.04E and prior) AND has XAML monitoring screen file loading enabled, allowing untrusted XAML files to be deserialized.

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.95.210.01
Interim mitigation

Apply vendor-supplied patches when available; until then, enforce strict controls on loading monitoring screen files from untrusted sources, disable XAML file loading if possible, and educate users about not opening suspicious screen files.

Fix this in Genesis64 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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