dbcve.org
Genesis64Application · Iconics

CVE-2022-23130

MEDIUM · 5.5 CVSS v3.1 Published 2022-01-21
Fix available
A fix is available. Upgrade to after 10.97 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Buffer Over-read vulnerability in Mitsubishi Electric MC Works64 versions 4.00A to 4.04E, Mitsubishi Electric GENESIS64 versions 10.97 and prior, Mitsubishi Electric Iconics Digital Solutions GENESIS64 versions 10.97 and prior, Mitsubishi Electric ICONICS Suite versions 10.97 and prior, Mitsubishi Electric Iconics Digital Solutions ICONICS Suite versions 10.97 and prior, Mitsubishi Electric GENESIS32 versions 9.7 and prior, and Mitsubishi Electric Iconics Digital Solutions GENESIS32 versions 9.7 and prior allows an attacker to cause a DoS condition in the database server by getting a legitimate user to import a configuration file containing specially crafted stored procedures into GENESIS64, ICONICS Suite, MC Works64, or GENESIS32 and execute commands against the database from GENESIS64, ICONICS Suite, MC Works64, or GENESIS32.

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 · moderate confidence

Buffer over-read vulnerability in Mitsubishi Electric/ICONICS suite products (GENESIS64, ICONICS Suite, MC Works64, GENESIS32) allows an attacker to cause denial of service in the database server by tricking a legitimate user into importing a configuration file containing specially crafted stored procedures that can then be executed against the database.

MitigationRestrict configuration file imports to only verified sources, implement strict input validation on imported configuration files, and update to vendor-patched versions when available. Consider network segmentation to isolate database servers from affected application tiers.

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
Hyper HistorianApplication
Affected:<= 10.97
Mc Works64Application
Affected:>= 10.95.201.23, <= 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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. Check Genesis64 version
    Locate the GENESIS64 installation directory and check the version information in the About dialog or in the version.dll file properties. Common paths include C:\Program Files\ICONICS\GENESIS64\ or check the Windows Programs and Features list.
    Affected if Installed version is 10.97 or lower (any version <= 10.97)
  2. Check Hyper Historian version
    Open Hyper Historian Administrator or check the Windows Programs and Features for the installed version. The product typically installs under C:\Program Files\ICONICS\HyperHistorian\.
    Affected if Installed version is 10.97 or lower (any version <= 10.97)
  3. Check MC Works64 version
    Access the MC Works64 application information through Windows Programs and Features or check the installation directory for version details. Look for versions between 10.95.201.23 and 10.95.210.01 inclusive.
    Affected if Installed version is between 10.95.201.23 and 10.95.210.01 inclusive
  4. Verify configuration import functionality
    Check if the configuration file import feature is accessible in the affected applications. Look for import options in the enterprise administration tools, Workbench, or Database Manager components that allow importing stored procedures or configuration files.
    Affected if Configuration file import for stored procedures is available and not restricted
  5. Assess database server exposure
    Identify if the application is configured to connect to a backend database server (SQL Server or similar) and check network accessibility of the database port.
    Affected if The application connects to a database server and that server is network-accessible from the application tier

You are affected if any of the products (Genesis64, Hyper Historian, or MC Works64) are installed at versions within the affected ranges AND the configuration file import feature is accessible to users who could be tricked into importing malicious files.

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

Restrict configuration file imports to only verified sources, implement strict input validation on imported configuration files, and update to vendor-patched versions when available. Consider network segmentation to isolate database servers from affected application tiers.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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