dbcve.org
CoreosOperating system · Mitsubishielectric

CVE-2020-5645

HIGH · 7.5 CVSS v3.1 Published 2020-11-06
Fix available
A fix is available. Upgrade to after 05.65.00.bd 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
Session fixation 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 a remote unauthenticated attacker 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 · moderate confidence

Session fixation vulnerability in the TCP/IP function of Mitsubishi Electric GOT 1000 series GT14 HMI panels (CoreOS 05.65.00.BD and earlier) allows a remote unauthenticated attacker to stop network functions via specially crafted packets. The vulnerability enables session hijacking through predictable or controllable session identifiers, leading to network service disruption.

MitigationUpdate the affected GOT 1000 GT14 model firmware to a version beyond CoreOS 05.65.00.BD. If patching is not immediately possible, isolate these HMI devices behind a firewall or VLAN to limit external attack surface.

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

CVSS:3.1/AV:N/AC:L/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. Confirm device model is GT14 from GOT 1000 series
    Identify the exact model number through the device's front label, management interface, or network discovery. Only GT14 models are affected.
    Affected if The device is a Mitsubishi Electric GOT 1000 series GT14 HMI panel
  2. Determine the CoreOS version
    Access the device management interface or system information page and locate the CoreOS firmware version. Compare the installed version to 05.65.00.BD.
    Affected if CoreOS version is 05.65.00.BD or earlier
  3. Verify TCP/IP networking is enabled
    Check the device network configuration settings to confirm the TCP/IP function is active. This vulnerability resides in the TCP/IP stack.
    Affected if TCP/IP networking is enabled on the device
  4. Assess network exposure
    Determine if the HMI panel is directly accessible from untrusted networks. Check firewall rules, VLAN placement, and whether external hosts can reach the device on TCP/IP ports.
    Affected if The device TCP/IP interface is reachable from untrusted or external networks without firewall protection
  5. Review session configuration
    Inspect session management settings in the device network or security configuration. Look for session identifier handling in TCP/IP-related settings.
    Affected if Session identifiers can be predicted, controlled, or are exposed to network attackers

You are affected if you have a GT14 HMI panel with CoreOS version 05.65.00.BD or earlier, and TCP/IP networking is enabled and accessible from a network where an attacker could intercept or manipulate session identifiers.

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 affected GOT 1000 GT14 model firmware to a version beyond CoreOS 05.65.00.BD. If patching is not immediately possible, isolate these HMI devices behind a firewall or VLAN to limit external attack surface.

Fix this in Coreos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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