dbcve.org
Genesis64Application · Iconics

CVE-2022-33317

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
Inclusion of Functionality from Untrusted Control Sphere 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 script 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

Mitsubishi Electric GENESIS64 and related suites contain an unauthenticated file inclusion vulnerability where the application loads monitoring screen files without proper validation of their contents. An attacker can embed malicious script code within these screen files, leading to arbitrary code execution when a victim opens the file.

MitigationOrganizations should upgrade to patched versions when available, implement file integrity validation (e.g., cryptographic signing of legitimate screen files), and train users to only open monitoring screen files from trusted sources.

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 installed Iconics Genesis64 version
    Check the installed version through Windows Programs and Features, or run 'Get-ItemProperty' on the installation directory if known. Compare the version number to 10.97 or 10.97.1.
    Affected if The installed version is exactly 10.97 or 10.97.1
  2. Identify installed Mitsubishi Electric Mc Works64 version
    Check the installed version through Windows Programs and Features, or check the application's About/Version information. Compare to version 10.95.210.01.
    Affected if The installed version is 10.95.210.01 or earlier
  3. Locate monitoring screen files
    Search for common screen file extensions used by GENESIS64 (typically .gdf, .gx, or similar graphics files) in the application data directories or project folders.
    Affected if Screen files exist and can be opened by the application
  4. Inspect screen file loading configuration
    Examine application configuration files or project settings that control how monitoring screen files are loaded and whether any validation or integrity checking is performed.
    Affected if No validation or integrity checking is configured for screen files
  5. Verify network exposure of screen file handling
    Check if the web server or visualization interface that serves GENESIS64 screens is exposed to untrusted networks, as the vulnerability allows unauthenticated file inclusion.
    Affected if The application interface handling screen files is accessible without authentication

You are affected if you have Iconics Genesis64 version 10.97 or 10.97.1, or Mc Works64 version 10.95.210.01 or earlier, and the application loads monitoring screen files without validation.

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

Organizations should upgrade to patched versions when available, implement file integrity validation (e.g., cryptographic signing of legitimate screen files), and train users to only open monitoring screen files from trusted sources.

Fix this in Genesis64 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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