dbcve.org
Genesis64Application · Iconics

CVE-2022-23129

MEDIUM · 5.5 CVSS v3.1 Published 2022-01-21
Fix available
A fix is available. Upgrade to 10.95.210.01 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Plaintext Storage of a Password vulnerability in Mitsubishi Electric MC Works64 versions 4.04E (10.95.210.01) and prior and ICONICS GENESIS64 versions 10.90 to 10.97 allows a local authenticated attacker to gain authentication information and to access the database illegally. This is because when configuration information of GridWorX, a database linkage function of GENESIS64 and MC Works64, is exported to a CSV file, the authentication information is saved in plaintext, and an attacker who can access this CSV file can gain the authentication information.

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

The GridWorX database linkage function in Mitsubishi Electric MC Works64 and ICONICS GENESIS64 saves authentication credentials in plaintext when exporting configuration to CSV files. A local authenticated attacker with access to these exported CSV files can retrieve the plaintext credentials and gain unauthorized database access.

MitigationRestrict access to exported CSV files and implement encryption for stored credentials; contact vendor for patched versions.

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.90, <= 10.97
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 product version
    Check the version of either Iconics GENESIS64 or Mitsubishi Electric MC Works64 installed in your environment using the system's About or version information panel
    Affected if The version is GENESIS64 >= 10.90 and <= 10.97, or MC Works64 < 10.95.210.01
  2. Determine if GridWorX is configured
    Locate GridWorX configuration files or check the GridWorX database linkage settings within the application
    Affected if GridWorX database linkage feature is configured and connected to a database
  3. Locate exported CSV configuration files
    Search for CSV files created by GridWorX export functionality in the application data directories, project folders, or configured export locations
    Affected if Exported CSV files from GridWorX configuration exist on the system
  4. Inspect CSV files for plaintext credentials
    Open the exported CSV files and examine them for database connection strings, usernames, and passwords stored in cleartext
    Affected if The CSV files contain unencrypted username and password fields for database authentication
  5. Check file access permissions
    Review file system permissions on CSV export directories to determine if unauthorized local users could access these files
    Affected if CSV files with credentials are accessible to users other than the intended administrator account

You are affected if you run a vulnerable version of GENESIS64 or MC Works64 with GridWorX configured and have exported database configuration to CSV files that contain plaintext credentials accessible to local users.

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.

dbcve · scoped
Upgrade available Upgrade to 10.95.210.01 or later
Fixed in 10.95.210.01
Interim mitigation

Restrict access to exported CSV files and implement encryption for stored credentials; contact vendor for patched versions.

Recommended fix Moderate confidence

Genesis64: version > 10.97 (e.g., 10.97.1 or latest); Mc Works64: version >= 10.95.210.01 (4.04E or newer)

  1. 1. Identify the currently installed Genesis64 or Mc Works64 version in your environment.
  2. 2. Navigate to the official Mitsubishi Electric support page or contact their technical support to obtain the patched version.
  3. 3. For Mc Works64: Upgrade to version 10.95.210.01 or later (which is version 4.04E or newer).
  4. 4. For Genesis64: Upgrade to version 10.97.1 or later, or the latest available version that supersedes 10.97.
  5. 5. After upgrading, verify that the GridWorX export function no longer stores authentication credentials in plaintext.
  6. 6. If available, apply any additional security patches or hardening configurations recommended by Mitsubishi Electric.
Caveat Review release notes for any breaking changes between current version and target upgrade version; ensure compatibility with existing configurations and dependent systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Genesis64 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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