CVE-2022-40264
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in ICONICS/Mitsubishi Electric GENESIS64 versions 10.96 to 10.97.2 allows an unauthenticated attacker to create, tamper with or destroy arbitrary files by getting a legitimate user import a project package file crafted by the attacker.
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 confidencePath traversal vulnerability in ICONICS/Mitsubishi Electric GENESIS64 SCADA software versions 10.96-10.97.2 allows an unauthenticated attacker to craft a malicious project package file that, when imported by a legitimate user, enables creation, tampering with or destruction of arbitrary files on the system due to insufficient path validation during the import process.
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.96, <= 10.97.2CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Verify if ICONICS Genesis64 is installedCheck for Genesis64 installation directories (commonly under C:\Program Files\ICONICS or C:\Program Files (x86)\ICONICS) or look for Iconics-related services running on the systemAffected if Genesis64 SCADA software is present on the system
-
Determine the installed Genesis64 versionLocate version information in the application's About dialog, help menu, or check installation metadata (such as the executable's properties or installer records)Affected if The discovered version falls within the range >= 10.96 and <= 10.97.2
-
Assess exposure of project import functionalityDetermine whether the project import feature is accessible to users or network-connected systems. For web-based deployments, check if the import interface (often via Workbench or WebHMI) is exposed on the networkAffected if The import functionality is accessible to untrusted users or network paths without additional access controls
-
Confirm the vulnerability precondition existsVerify that users with access to the system can import project package files into Genesis64. This is typically done through the Workbench application or admin interfacesAffected if Users can import project packages without additional hardening or network restrictions
The environment is affected if Genesis64 version 10.96 through 10.97.2 is installed AND the project import functionality is accessible to the user or network actors who could supply a malicious package.
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 dataUpgrade to GENESIS64 version 10.97.3 or later which contains the vendor patch; implement network segmentation and restrict import functionality to trusted sources until patching is complete.
- Consultation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40264 — 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-40264 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