dbcve.org
Gx Works3Application · Mitsubishielectric

CVE-2022-29831

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 Password vulnerability in Mitsubishi Electric Corporation GX Works3 versions from 1.015R to 1.095Z allows a remote unauthenticated attacker to obtain information about the project file for MELSEC safety CPU modules.

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

A hard-coded password vulnerability in Mitsubishi Electric GX Works3 versions 1.015R to 1.095Z allows remote unauthenticated attackers to access project file information for MELSEC safety CPU modules. The hard-coded credential bypasses authentication controls, enabling unauthorized disclosure of sensitive industrial automation project data.

MitigationUpdate to a patched version of GX Works3 when available, or contact Mitsubishi for specific remediation guidance. Restrict network exposure of affected systems and implement additional authentication layers for safety CPU module project files.

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.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. Verify GX Works3 is installed
    Check for GX Works3 in Windows Programs and Features, or look for its installation directory (typically under C:\Program Files\Mitsubishi\ or C:\Program Files (x86)\Mitsubishi\)
    Affected if GX Works3 is present on the system
  2. Locate the installed version number
    Open GX Works3 and navigate to the Help menu, or right-click the executable file in the installation folder and view Properties > Details. The version is also sometimes visible in the application's title bar or startup splash screen
    Affected if Unable to determine version - manual verification needed
  3. Compare version against affected ranges
    Match your installed version (format like 1.015R, 1.086Q, 1.087R) against the affected ranges: 1.015R through 1.086Q inclusive, or 1.087R and later
    Affected if Installed version is 1.015R to 1.086Q inclusive OR 1.087R or higher (all versions in the ranges listed)
  4. Assess network exposure of the system
    Determine if the system running GX Works3 or hosting project files is accessible from untrusted network locations. Check firewall rules, VPN configuration, and whether the system has public IP addresses
    Affected if The system is network-accessible from untrusted or public networks

A user is affected if GX Works3 is installed with any version from 1.015R through 1.086Q or version 1.087R and later, and the system or project files could be accessed remotely by an attacker.

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

Update to a patched version of GX Works3 when available, or contact Mitsubishi for specific remediation guidance. Restrict network exposure of affected systems and implement additional authentication layers for safety CPU module project files.

Recommended fix Moderate confidence

GX Works3 version 1.095Z or later

  1. Visit the official Mitsubishi Electric support page for GX Works3 to download the latest version
  2. Ensure you are running GX Works3 version 1.095Z or later, which contains the fix for this vulnerability
  3. Before upgrading, back up all existing project files
  4. After upgrading, verify that the hard-coded password vulnerability is remediated by confirming project files for MELSEC safety CPU modules are no longer accessible without proper authentication
  5. Consult Mitsubishi Electric's release notes for any additional security updates included in the upgrade
Caveat Review release notes for any changes to project file compatibility or functionality that may affect existing workflows

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

Fix this in Gx Works3 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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