dbcve.org
EzsocketApplication · Mitsubishielectric

CVE-2023-6942

HIGH · 7.5 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 →
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
Missing Authentication for Critical Function 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 bypass authentication by sending specially crafted packets and connect to the products 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

This vulnerability allows remote unauthenticated attackers to bypass authentication in multiple Mitsubishi Electric industrial software products by sending specially crafted packets. The missing authentication check on a critical function enables illegal connections to affected systems without credentials.

MitigationApply available vendor patches or updates to all affected product versions. If patches are unavailable, implement network segmentation and restrict access to affected systems via firewall rules to limit exposure.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 Electric software
    Open Windows Control Panel > Programs and Features, or check C:\Program Files and C:\Program Files (x86) for folders named Ezsocket, FR Configurator2, GOT1000, GOT2000, GX Works2, GX Works3, MC Works64, or Melsoft Navigator
    Affected if Any of these products appear in installed programs or directories
  2. Check Ezsocket version
    If installed, right-click the Ezsocket executable (typically in Program Files\Mitsubishi Electric\Ezsocket), select Properties, and view the Version tab
    Affected if Version is 3.0 or higher (all versions 3.0 and above are affected)
  3. Check GX Works2 version
    If installed, open GX Works2 and go to Help > Version Information, or right-click the executable in Program Files\Mitsubishi Electric\GX Works2 and check Properties > Details for version
    Affected if Version is 1.11m or higher (versions below 1.11m are not affected)
  4. Check Melsoft Navigator version
    If installed, right-click the Melsoft Navigator executable in Program Files\Mitsubishi Electric\Melsoft Navigator and view Properties > Details for version number
    Affected if Version is 1.04e or higher (versions below 1.04e are not affected)
  5. Check FR Configurator2, GOT1000, GOT2000, GX Works3, and MC Works64 versions
    If any of these are installed (check Program Files\Mitsubishi Electric folder), right-click the respective executable and view Properties > Details for version
    Affected if Any version is installed (these products are affected in all versions)

If any of the eight affected products are installed and the version falls within or above the specified ranges (or is any version for products with 'all versions'), the system is affected by this authentication bypass vulnerability.

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 available vendor patches or updates to all affected product versions. If patches are unavailable, implement network segmentation and restrict access to affected systems via firewall rules to limit exposure.

Fix this in Ezsocket Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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