dbcve.org
CoreosOperating system · Mitsubishielectric

CVE-2020-5648

CRITICAL · 9.8 CVSS v3.1 Published 2020-11-06
Fix available
A fix is available. Upgrade to after 05.65.00.bd or later.
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
Improper neutralization of argument delimiters in a command ('Argument Injection') vulnerability in TCP/IP function included in the firmware of GT14 Model of GOT 1000 series (GT1455-QTBDE CoreOS version "05.65.00.BD" and earlier, GT1450-QMBDE CoreOS version "05.65.00.BD" and earlier, GT1450-QLBDE CoreOS version "05.65.00.BD" and earlier, GT1455HS-QTBDE CoreOS version "05.65.00.BD" and earlier, and GT1450HS-QMBDE CoreOS version "05.65.00.BD" and earlier) allows unauthenticated attackers on adjacent network to stop the network functions of the products via a specially crafted packet.

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

Argument injection vulnerability in the TCP/IP function of Mitsubishi Electric GT14 Model GOT1000 series HMI panels allows unauthenticated attackers on adjacent networks to send specially crafted packets that can stop network functions. The vulnerability stems from improper neutralization of argument delimiters in commands.

MitigationUpdate the CoreOS firmware to a version later than 05.65.00.BD when available from the vendor. Until patches are available, implement network segmentation to restrict access to the adjacent network and monitor for anomalous packets targeting the TCP/IP function.

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
CoreosOperating system
Affected:<= 05.65.00.bd

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 the device model
    Locate the HMI panel and verify it is a Mitsubishi Electric GT14 Model GOT1000 series device. Check the product label or system information screen for the exact model number.
    Affected if The device is not a GT14 Model GOT1000 series HMI panel
  2. Check the CoreOS version
    Access the device system settings or firmware information page. Navigate to the CoreOS version display (typically found in System > Device Information or similar menu path on the HMI). Record the version number displayed.
    Affected if The CoreOS version is 05.65.00.bd or any version lower than 05.65.00.bd
  3. Verify TCP/IP network function is enabled
    Access the device network settings menu. Check if TCP/IP communication is configured and enabled. Look for settings under Network Setup or Ethernet Configuration on the HMI device.
    Affected if TCP/IP networking is enabled and configured on the device
  4. Assess network exposure
    Determine if the device is connected to a network that is accessible to unauthenticated attackers on adjacent networks. Check the network topology and whether the HMI is on a segmented or directly accessible network segment.
    Affected if The device TCP/IP interface is reachable from an adjacent network without proper segmentation or access controls

The device is affected if it is a GT14 Model GOT1000 series HMI running CoreOS version 05.65.00.bd or lower, with TCP/IP function enabled and accessible from an adjacent network.

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
Upgrade available Upgrade to a release after 05.65.00.bd
Interim mitigation

Update the CoreOS firmware to a version later than 05.65.00.BD when available from the vendor. Until patches are available, implement network segmentation to restrict access to the adjacent network and monitor for anomalous packets targeting the TCP/IP function.

Fix this in Coreos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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