CVE-2020-5599
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 · uneditedTCP/IP function included in the firmware of Mitsubishi Electric GOT2000 series (CoreOS with version -Y and earlier installed in GT27 Model, GT25 Model, and GT23 Model) contains an improper neutralization of argument delimiters in a command ('Argument Injection') vulnerability, which may allow a remote attacker to stop the network functions of the products or execute a malicious program 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 confidenceA critical argument injection vulnerability exists in the TCP/IP function of Mitsubishi Electric GOT2000 series HMI firmware (CoreOS version -Y and earlier). The improper neutralization of argument delimiters allows remote attackers to send specially crafted packets that can either stop network functions (DoS) or execute arbitrary malicious programs on affected GT27, GT25, and GT23 models.
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<= yCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the GOT2000 model numberLocate the model identification label on the physical HMI device or check the device documentation/system information screen. Confirm it is one of the affected models: GT27, GT25, or GT23.Affected if The model is GT27, GT25, or GT23. Other GOT2000 models are not affected by this specific CVE.
-
Determine the CoreOS firmware versionAccess the device system information or firmware management menu on the GOT2000 HMI. Look for the CoreOS version displayed (typically shown as a letter designation such as -Y or earlier).Affected if The CoreOS version is -Y or any version earlier than -Y (for example, -X, -W, etc.). Versions after -Y are not affected.
-
Verify TCP/IP networking is configuredCheck the device network settings or communication configuration. Confirm that TCP/IP protocol stack is enabled and the device has an IP address assigned.Affected if TCP/IP networking is active. If the device has TCP/IP disabled and is not network-connected, the attack surface is reduced though the underlying vulnerable code may still be present.
Your environment is affected if you have a GT27, GT25, or GT23 model with CoreOS version -Y or earlier that has TCP/IP networking enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor-supplied patched CoreOS firmware update to all affected GOT2000 devices. Prioritize devices exposed to untrusted networks given the remote attack vector and critical CVSS score.
- Consultation6.0 h
- Implementation10.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5599 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-5599 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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