dbcve.org
Gx Works3Application · Mitsubishielectric

CVE-2022-29829

HIGH · 7.5 CVSS v3.1 Published 2022-11-25
Fix available
A fix is available. Upgrade to after 1.086q or later.
See remediation →
84/100
Remediation priority · High
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
Use of Hard-coded Cryptographic Key vulnerability in Mitsubishi Electric GX Works3 versions from 1.000A to 1.090U, GT Designer3 Version1 (GOT2000) versions from 1.122C to 1.290C, Motion Control Setting(GX Works3 related software) versions from 1.035M to 1.042U, and MT Works2 versions from 1.100E to 1.200J allows a remote unauthenticated attacker to disclose sensitive information. As a result, unauthenticated users may view programs and project files or execute programs illegally.

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

Mitsubishi Electric GX Works3, GT Designer3, Motion Control Setting, and MT Works2 contain a hard-coded cryptographic key embedded in the software. An unauthenticated remote attacker can discover this key and use it to decrypt sensitive project data, view proprietary programs, and potentially execute unauthorized programs on affected systems.

MitigationApply vendor patches or updates to all affected software versions. If patches are unavailable, implement network segmentation, restrict access to engineering workstations, and monitor for unauthorized access attempts using the hard-coded key.

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
Gx Works3Application
Affected:>= 1.000a, <= 1.011m>= 1.015r, <= 1.086q>= 1.087r

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
None

CVSS:3.1/AV:N/AC:L/PR:N/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 Mitsubishi engineering software
    Check Programs and Features (Windows) or the application itself for GX Works3, GT Designer3, Motion Control Setting, or MT Works2
    Affected if Any of these four products are installed on the system
  2. Determine installed version of the software
    Open the software and navigate to Help > Version Information, or right-click the application in Programs and Features and select Properties to view the version details
    Affected if The displayed version falls within the affected ranges provided by the vendor
  3. Compare version against affected ranges
    Cross-reference the installed version number against the affected version ranges: 1.000a through 1.011m, 1.015r through 1.086q, or 1.087r and later
    Affected if The installed version is any of the versions listed as affected
  4. Assess exposure to network threats
    Review network accessibility of the engineering workstation and whether the software handles sensitive project data or proprietary programs
    Affected if The affected software is accessible on the network or handles confidential project information

If any of the four Mitsubishi Electric engineering software products are installed and the version falls within the affected ranges, the system contains the hard-coded cryptographic key and sensitive project data may be at risk of unauthorized decryption.

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 a release after 1.086q
Interim mitigation

Apply vendor patches or updates to all affected software versions. If patches are unavailable, implement network segmentation, restrict access to engineering workstations, and monitor for unauthorized access attempts using the hard-coded key.

Recommended fix Moderate confidence

Upgrade to GX Works3 version 1.091V or later (the first fixed release after the affected version range ending at 1.090U)

  1. 1. Identify the current installed version of GX Works3 by opening the software and checking 'Help' > 'Product Information' or checking the installed programs list in Windows Control Panel.
  2. 2. Download the latest version of GX Works3 from the official Mitsubishi Electric website (www.mitsubishielectric.com) or your authorized distributor.
  3. 3. Before upgrading, back up all existing project files, programs, and configurations. Locate the project file storage directory (typically in Documents > GX Works3 or a custom designated path) and create a complete backup.
  4. 4. Close all instances of GX Works3 and ensure no Mitsubishi related software is running.
  5. 5. Run the installer for the latest downloaded version with administrator privileges.
  6. 6. Follow the on-screen installation wizard instructions, choosing 'Upgrade' or 'Repair' when prompted to preserve settings.
  7. 7. After installation completes, verify the new version number matches the intended fixed release.
  8. 8. Test that existing project files open correctly and that the hardcoded cryptographic key issue is resolved by confirming project files are no longer accessible without proper authentication.
Caveat Review release notes for potential compatibility changes with existing project files and PLC hardware configurations before production deployment

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

Fix this in Gx Works3 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,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 $12,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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