# CVE-2021-20601: Business logic in GOT2000 series GT27 model; GOT2000 series GT25 model; GOT2000 series GT23 model; GOT2000 series GT21 model; GOT SIMPLE series GS21 model; GT SoftGOT2000

> Remote unauthenticated attackers can bypass input validation to write out-of-range values, potentially causing device malfunction or denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-j5w5-24wj-99v2

## What is CVE-2021-20601?

CVE-2021-20601 is a high-severity vulnerability in GOT2000 series GT27 model; GOT2000 series GT25 model; GOT2000 series GT23 model; GOT2000 series GT21 model; GOT SIMPLE series GS21 model; GT SoftGOT2000, published on 23 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper input validation vulnerability in GOT2000 series GT27 model all versions, GOT2000 series GT25 model all versions, GOT2000 series GT23 model all versions, GOT2000 series GT21 model all versions, GOT SIMPLE series GS21 model all versions, and GT SoftGOT2000 all versions allows an remote unauthenticated attacker to write a value that exceeds the configured input range limit by sending a malicious packet to rewrite the device value. As a result, the system operation may be affected, such as malfunction.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2021-20601?

It affects 50 products.


Products: Mitsubishielectric Got2000 Gt2103-Pmbd Firmware, Mitsubishielectric Got2000 Gt2103-Pmbds2 Firmware, Mitsubishielectric Got2000 Gt2103-Pmbds Firmware, Mitsubishielectric Got2000 Gt2103-Pmbls Firmware, Mitsubishielectric Got2000 Gt2104-Rtbd Firmware, Mitsubishielectric Got2000 Gt2107-Wtbd Firmware, Mitsubishielectric Got2000 Gt2308-Vtba Firmware, Mitsubishielectric Got2000 Gt2308-Vtbd Firmware, Mitsubishielectric Got2000 Gt2310-Vtba Firmware, Mitsubishielectric Got2000 Gt2310-Vtbd Firmware, Mitsubishielectric Got2000 Gt2505-Vtbd Firmware, Mitsubishielectric Got2000 Gt2505hs-Vtbd Firmware, Mitsubishielectric Got2000 Gt2506hs-Vtbd Firmware, Mitsubishielectric Got2000 Gt2507-Wtbd Firmware, Mitsubishielectric Got2000 Gt2507-Wtsd Firmware, Mitsubishielectric Got2000 Gt2507t-Wtsd Firmware, Mitsubishielectric Got2000 Gt2508-Vtba Firmware, Mitsubishielectric Got2000 Gt2508-Vtbd Firmware, Mitsubishielectric Got2000 Gt2508-Vtwa Firmware, Mitsubishielectric Got2000 Gt2508-Vtwd Firmware and 30 more.

## How do I fix CVE-2021-20601?

No fix has been published for CVE-2021-20601 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-20601 being exploited?

There is no known exploitation of CVE-2021-20601 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-20601 and fix it if it is affected.

What it is: CVE-2021-20601 is a high-severity vulnerability in GOT2000 series GT27 model; GOT2000 series GT25 model; GOT2000 series GT23 model; GOT2000 series GT21 model; GOT SIMPLE series GS21 model; GT SoftGOT2000, published on 23 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-20601 in the wild and no public exploit code.

Affected product: GOT2000 series GT27 model; GOT2000 series GT25 model; GOT2000 series GT23 model; GOT2000 series GT21 model; GOT SIMPLE series GS21 model; GT SoftGOT2000. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-20601/ (Markdown: https://insights.sbomify.com/CVE-2021-20601/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-20601
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-20601
- OSV: https://osv.dev/vulnerability/CVE-2021-20601

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-20601/
Summaries are generated and may contain mistakes; the official description above is the record.