dbcve.org
Genesis64Application · Iconics

CVE-2022-33319

CRITICAL · 9.1 CVSS v3.1 Published 2022-07-20
Fix available
A fix is available. Upgrade to after 10.95.210.01 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
Out-of-bounds Read 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, Mitsubishi Electric GENESIS32 versions 9.7 and prior, Mitsubishi Electric Iconics Digital Solutions GENESIS32 versions 9.7 and prior, and Mitsubishi Electric MC Works64 versions 4.04E and prior allows a remote unauthenticated attacker to disclose information on memory or cause a Denial of Service (DoS) condition by sending specially crafted packets to the GENESIS64, ICONICS Suite, GENESIS32, or MC Works64 server.

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

An out-of-bounds read vulnerability exists in Mitsubishi Electric GENESIS64, ICONICS Suite, GENESIS32, and MC Works64 server components. Remote unauthenticated attackers can send specially crafted packets to trigger the vulnerability, potentially disclosing sensitive memory contents or causing a Denial of Service condition.

MitigationApply vendor-provided patches for affected versions (GENESIS64/ICONICS Suite 10.97 to 10.97.1, GENESIS32 9.7 and prior, MC Works64 4.04E and prior). If patches unavailable, isolate affected systems via network segmentation and restrict external access to server ports.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 installed Mitsubishi Electric or ICONICS suite products
    Check installed programs for GENESIS64, ICONICS Suite, GENESIS32, or MC Works64. On Windows, review Add/Remove Programs or the installation directory for these product names.
    Affected if Any of these products are installed on the system
  2. Determine the installed version
    Open the product's About or Help section, check the installation directory for version information, or query the program's executable file properties for the version number.
    Affected if Version is 10.97, 10.97.1 for Genesis64/ICONICS Suite, or MC Works64 version <= 10.95.210.01
  3. Verify if server components are running
    Open Services console (services.msc) and look for services related to GENESIS64, ICONICS, GENESIS32, or MC Works64 server components. Check if these services are in a Running state.
    Affected if The vulnerable server components are running as active services
  4. Check network exposure of the server service
    Use netstat -an or review firewall rules to determine if the affected product's server ports are listening on network interfaces accessible from external sources. Identify which ports the product uses (consult product documentation for specific port numbers).
    Affected if The server component ports are exposed to untrusted network segments or the internet

The system is affected if any of the four products (Genesis64, ICONICS Suite, GENESIS32, MC Works64) are installed with a vulnerable version and the server component is network-accessible.

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-provided patches for affected versions (GENESIS64/ICONICS Suite 10.97 to 10.97.1, GENESIS32 9.7 and prior, MC Works64 4.04E and prior). If patches unavailable, isolate affected systems via network segmentation and restrict external access to server ports.

Fix this in Genesis64 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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