dbcve.org
Gc Enet Com FirmwareOperating system · Mitsubishielectric

CVE-2023-1285

MEDIUM · 5.9 CVSS v3.1 Published 2023-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
Signal Handler Race Condition vulnerability in Mitsubishi Electric India GC-ENET-COM whose first 2 digits of 11-digit serial number of unit are "16" allows a remote unauthenticated attacker to cause a denial-of-service (DoS) condition in Ethernet communication by sending a large number of specially crafted packets to any UDP port when GC-ENET-COM is configured as a Modbus TCP Server. The communication resumes only when the power of the main unit is turned off and on or when the GC-ENET-COM is hot-swapped from the main unit.

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

A signal handler race condition vulnerability in Mitsubishi Electric India GC-ENET-COM devices with serial numbers starting with '16' allows remote unauthenticated attackers to cause denial-of-service by sending specially crafted packets to UDP ports when the device is configured as a Modbus TCP Server. The attack triggers a race condition that disrupts Ethernet communication, requiring a power cycle or hot-swap to restore functionality.

MitigationImplement network segmentation and firewall rules to restrict unsolicited UDP traffic to the GC-ENET-COM device. Since this is a firmware-level race condition, contact Mitsubishi Electric for an official firmware patch to address the underlying vulnerability.

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
Gc Enet Com FirmwareOperating system
Affected:all versions

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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 GC-ENET-COM device in your network
    Locate and inventory all Mitsubishi Electric GC-ENET-COM devices on your network. This is a network gateway/comms module used for Ethernet serial communication.
    Affected if You have any GC-ENET-COM device deployed in your environment.
  2. Check device serial number prefix
    Retrieve the serial number from the physical device label or via device management interface. Verify if the serial number begins with '16'.
    Affected if The serial number starts with '16' (e.g., 16XXXXXX). Only serial numbers with this prefix are vulnerable.
  3. Verify Modbus TCP Server configuration is enabled
    Access the device configuration panel and check if the Modbus TCP Server feature is enabled. This is typically found in the communication settings or protocol configuration section.
    Affected if Modbus TCP Server is actively enabled on the device. The vulnerability only triggers when this feature is configured.
  4. Assess UDP port exposure
    Review firewall rules and network accessibility to determine if UDP ports on the GC-ENET-COM device are exposed to untrusted networks or the internet. Check for open UDP ports in the device's port configuration.
    Affected if UDP ports on the device are reachable from untrusted or external network segments without filtering.
  5. Check for communication disruption symptoms
    Monitor Ethernet communication status on the GC-ENET-COM device. Look for intermittent connectivity loss, unresponsive Ethernet interfaces, or unexplained communication failures that require power cycle to restore.
    Affected if Ethernet communication is disrupted and requires power cycle or hot-swap to restore functionality.

You are affected if you have a GC-ENET-COM device with a serial number starting with '16', with Modbus TCP Server enabled, and with exposed UDP ports reachable from untrusted networks.

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

Implement network segmentation and firewall rules to restrict unsolicited UDP traffic to the GC-ENET-COM device. Since this is a firmware-level race condition, contact Mitsubishi Electric for an official firmware patch to address the underlying vulnerability.

Fix this in Gc Enet Com Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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