CVE-2022-33320
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 · uneditedDeserialization 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 project configuration file including malicious XML 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 confidenceA deserialization vulnerability in Mitsubishi Electric GENESIS64, ICONICS Suite, and MC Works64 allows unauthenticated attackers to execute arbitrary code by tricking users into loading malicious project configuration files containing specially crafted XML. The application deserializes untrusted XML data without proper validation, leading to code execution.
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= 10.97= 10.97.1<= 10.95.210.01CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed productCheck the system for Iconics Genesis64 or Mitsubishi Electric MC Works64 installation directories and executables. Common locations include C:\Program Files\ICONICS\ or C:\Program Files\Mitsubishi Electric\MC Works64\Affected if Either Iconics Genesis64 or Mitsubishi MC Works64 is installed on the system
-
Check Iconics Genesis64 versionOpen Windows Control Panel > Programs and Features, or right-click the Genesis64 executable and select Properties > Details to view the file version. Compare against affected versions 10.97 and 10.97.1Affected if The installed version is exactly 10.97 or 10.97.1
-
Check Mitsubishi MC Works64 versionOpen Windows Control Panel > Programs and Features, or right-click the MC Works64 executable and select Properties > Details to view the file version. Compare against affected version <= 10.95.210.01Affected if The installed version is 10.95.210.01 or lower
-
Assess XML project file usageDetermine whether users regularly import or load project configuration files (.xml, .iop, .config files) into the affected application. Check recent file access logs or the application's recent projects listAffected if The application is used to load or import project configuration files from any source
-
Inspect project configuration filesExamine any .xml or project configuration files in the application data directories for unexpected or suspicious XML content, especially serialized objects or binary data within XML tagsAffected if Untrusted or suspicious project configuration files are present on the system
A user is affected if either Iconics Genesis64 version 10.97/10.97.1 or Mitsubishi MC Works64 version 10.95.210.01 or lower is installed AND the application is used to load or import project configuration files.
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 dataUsers should not open untrusted project configuration files from unverified sources. Apply vendor patches when available and implement network segmentation to limit exposure of affected systems.
- Consultation8.0 h
- Implementation40.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33320 — 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-33320 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