CVE-2020-5675
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 · uneditedOut-of-bounds read vulnerability in GT21 model of GOT2000 series (GT2107-WTBD V01.39.000 and earlier, GT2107-WTSD V01.39.000 and earlier, GT2104-RTBD V01.39.000 and earlier, GT2104-PMBD V01.39.000 and earlier, and GT2103-PMBD V01.39.000 and earlier), GS21 model of GOT series (GS2110-WTBD V01.39.000 and earlier, GS2107-WTBD V01.39.000 and earlier, GS2110-WTBD-N V01.39.000 and earlier, and GS2107-WTBD-N V01.39.000 and earlier), and Tension Controller LE7-40GU-L series (LE7-40GU-L Screen package data for CC-Link IEF Basic V1.00, LE7-40GU-L Screen package data for MODBUS/TCP V1.00, and LE7-40GU-L Screen package data for SLMP V1.00) allows a remote attacker to cause a denial-of-service (DoS) condition by sending a specially crafted packet. As a result, deterioration of communication performance or a denial-of-service (DoS) condition of the TCP communication functions of the products may occur.
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 confidenceOut-of-bounds read vulnerability in Mitsubishi Electric GOT2000 GT21 series, GOT GS21 series, and Tension Controller LE7-40GU-L allows remote attackers to send specially crafted packets that cause the device to read memory outside buffer boundaries, leading to denial-of-service or communication performance degradation of TCP functions.
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<= 01.39.000<= 01.39.000<= 01.39.000<= 01.39.000<= 01.39.000<= 01.39.000<= 01.39.000= 1.00CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLocate the GOT2000 or GS21 series HMI or LE7-40GU-L Tension Controller on the network and confirm its exact model number (GT2107-WTBD, GT2107-WTSD, GT2104-RTBD, GT2104-PMBD, GT2103-PMBD, GS2110-WTBD, GS2107-WTBD, or LE7-40GU-L)Affected if The device model matches any of the affected models listed in the CVE
-
Check the installed firmware versionAccess the device's system information or firmware version display through the HMI interface or network management tool, or query the device via its built-in diagnostics or configuration softwareAffected if Firmware version is 01.39.000 or lower for GT21/GS21 series, or exactly 1.00 for LE7-40GU-L
-
Verify TCP communication is enabledCheck the device network configuration to confirm TCP/IP communication functions are enabled and activeAffected if TCP functions are enabled and the device is reachable over the network
-
Assess network exposureDetermine whether the device is directly accessible from untrusted networks or has open TCP ports exposed to external attackersAffected if The device TCP ports are accessible from untrusted or public networks without firewall protection
A user is affected if they have a GT21 series, GS21 series, or LE7-40GU-L device with firmware at or below 01.39.000 (or version 1.00 for LE7-40GU-L) that has TCP communication enabled and is exposed to network attack vectors.
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 dataUpdate firmware to a version newer than V01.39.000; if immediate patching is not possible, isolate affected devices behind firewalls or network segmentation to limit exposure to untrusted network traffic.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2020-5675 — 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-5675 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