dbcve.org
EzsocketApplication · Mitsubishielectric

CVE-2023-6943

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Mitsubishi Electric Corporation EZSocket versions 3.0 to 5.92, GT Designer3 Version1(GOT1000) versions 1.325P and prior, GT Designer3 Version1(GOT2000) versions 1.320J and prior, GX Works2 versions 1.11M to 1.626C, GX Works3 versions 1.106L and prior, MELSOFT Navigator versions 1.04E to 2.102G, MT Works2 versions 1.190Y and prior, MX Component versions 4.00A to 5.007H and MX OPC Server DA/UA all versions allows a remote unauthenticated attacker to execute a malicious code by RPC with a path to a malicious library while connected to the products.

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 multiple products contain an unsafe reflection vulnerability where externally-controlled RPC input is used to select classes or code to load. A remote unauthenticated attacker can specify a path to a malicious library, causing arbitrary code execution on the target system.

MitigationApply vendor patches for all affected products (EZSocket, GT Designer3, GX Works2/3, MELSOFT Navigator, MT Works2, MX Component, MX OPC Server) and restrict network access to RPC services to prevent unauthenticated exploitation.

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
EzsocketApplication
Affected:>= 3.0
Fr Configurator2Application
Affected:all versions
Got1000Application
Affected:all versions
Got2000Application
Affected:all versions
Gx Works2Application
Affected:>= 1.11m
Gx Works3Application
Affected:all versions
Mc Works64Application
Affected:all versions
Melsoft NavigatorApplication
Affected:>= 1.04e

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Mitsubishi Electric products
    Check Program Files or Program Files (x86) for Mitsubishi Electric software folders such as Ezsocket, FR Configurator2, GOT1000, GOT2000, GX Works2, GX Works3, MC Works64, or MELSOFT Navigator. Also check the Windows Add/Remove Programs list for these product names.
    Affected if Any of the listed Mitsubishi Electric products are installed on the system
  2. Determine installed version of EZSocket
    Open EZSocket application or check its About/Diagnostics section. Alternatively, locate the ezsckXX.dll file or installer log in the installation directory and note the version number.
    Affected if Version is 3.0 or higher (any version >= 3.0)
  3. Determine installed version of GX Works2
    Open GX Works2 and go to Help > Product Information, or locate the GX Works2 executable properties to view version details.
    Affected if Version is 1.11m or higher (any version >= 1.11m)
  4. Determine installed version of MELSOFT Navigator
    Open MELSOFT Navigator and check Help > Product Information, or view version via the executable properties.
    Affected if Version is 1.04e or higher (any version >= 1.04e)
  5. Verify if FR Configurator2, GOT1000, GOT2000, GX Works3, or MC Works64 are present
    Check installation directories or Add/Remove Programs for these products. These are affected in ALL versions regardless of version number.
    Affected if Any of these products are installed, at any version
  6. Check for exposed or enabled RPC services
    Review Windows Services for RPC-related services running, check firewall rules for open ports associated with Mitsubishi RPC communication (typically ports 5006-5007, 10900, 49152+), and verify if the affected software has RPC listening enabled in its configuration.
    Affected if RPC services are enabled and accessible on network interfaces, particularly if exposed to untrusted networks

If any Mitsubishi Electric product from the list is installed and its version falls within the affected ranges (or is any version for FR Configurator2, GOT1000, GOT2000, GX Works3, MC Works64), and RPC services are enabled, the environment is vulnerable to CVE-2023-6943.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for all affected products (EZSocket, GT Designer3, GX Works2/3, MELSOFT Navigator, MT Works2, MX Component, MX OPC Server) and restrict network access to RPC services to prevent unauthenticated exploitation.

Fix this in Ezsocket Scoped from the published advisory
  • Consultation12.0 h
  • Implementation20.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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