CVE-2021-20592 Vulnerability Analysis & Exploit Details

CVE-2021-20592
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2021-20592 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2021-20592 Details

Status: Modified

Last updated: 🕠 21 Nov 2024, 05:46 UTC
Originally published on: 🕘 05 Aug 2021, 21:15 UTC

Time between publication and last update: 1203 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE-2021-20592 Vulnerability Summary

CVE-2021-20592: Missing synchronization vulnerability in GOT2000 series GT27 model communication driver versions 01.19.000 through 01.39.010, GT25 model communication driver versions 01.19.000 through 01.39.010 and GT23 model communication driver versions 01.19.000 through 01.39.010 and GT SoftGOT2000 versions 1.170C through 1.256S allows a remote unauthenticated attacker to cause DoS condition on the MODBUS/TCP slave communication function of the products by rapidly and repeatedly connecting and disconnecting to and from the MODBUS/TCP communication port on a target. Restart or reset is required to recover.

Assessing the Risk of CVE-2021-20592

Access Complexity Graph

The exploitability of CVE-2021-20592 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2021-20592

With low attack complexity and no required privileges, CVE-2021-20592 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2021-20592, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2021-20592, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2021-20592 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2021-20592 poses no threat to data integrity.
  • Availability: High
    CVE-2021-20592 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.245% (probability of exploit)

EPSS Percentile: 64.38% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 35.620000000000005% of others.

CVE-2021-20592 References

External References

CWE Common Weakness Enumeration

CWE-662

CAPEC Common Attack Pattern Enumeration and Classification

  • Forced Deadlock CAPEC-25 The adversary triggers and exploits a deadlock condition in the target software to cause a denial of service. A deadlock can occur when two or more competing actions are waiting for each other to finish, and thus neither ever does. Deadlock conditions can be difficult to detect.
  • Leveraging Race Conditions CAPEC-26 The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
  • Leveraging Race Conditions via Symbolic Links CAPEC-27 This attack leverages the use of symbolic links (Symlinks) in order to write to sensitive files. An attacker can create a Symlink link to a target file not otherwise accessible to them. When the privileged program tries to create a temporary file with the same name as the Symlink link, it will actually write to the target file pointed to by the attackers' Symlink link. If the attacker can insert malicious content in the temporary file they will be writing to the sensitive file by using the Symlink. The race occurs because the system checks if the temporary file exists, then creates the file. The attacker would typically create the Symlink during the interval between the check and the creation of the temporary file.
  • Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions CAPEC-29 This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.

Vulnerable Configurations

  • cpe:2.3:a:mitsubishielectric:gt_softgot2000:1.170c:*:*:*:*:*:*:*
    cpe:2.3:a:mitsubishielectric:gt_softgot2000:1.170c:*:*:*:*:*:*:*
  • cpe:2.3:a:mitsubishielectric:gt_softgot2000:1.235v:*:*:*:*:*:*:*
    cpe:2.3:a:mitsubishielectric:gt_softgot2000:1.235v:*:*:*:*:*:*:*
  • cpe:2.3:a:mitsubishielectric:gt_softgot2000:1.236w:*:*:*:*:*:*:*
    cpe:2.3:a:mitsubishielectric:gt_softgot2000:1.236w:*:*:*:*:*:*:*
  • cpe:2.3:a:mitsubishielectric:gt_softgot2000:1.241b:*:*:*:*:*:*:*
    cpe:2.3:a:mitsubishielectric:gt_softgot2000:1.241b:*:*:*:*:*:*:*
  • cpe:2.3:a:mitsubishielectric:gt_softgot2000:1.256s:*:*:*:*:*:*:*
    cpe:2.3:a:mitsubishielectric:gt_softgot2000:1.256s:*:*:*:*:*:*:*
  • cpe:2.3:o:mitsubishielectric:got2000_gt27_firmware:01.19.000:*:*:*:*:*:*:*
    cpe:2.3:o:mitsubishielectric:got2000_gt27_firmware:01.19.000:*:*:*:*:*:*:*
  • cpe:2.3:o:mitsubishielectric:got2000_gt27_firmware:01.39.010:*:*:*:*:*:*:*
    cpe:2.3:o:mitsubishielectric:got2000_gt27_firmware:01.39.010:*:*:*:*:*:*:*
  • cpe:2.3:h:mitsubishielectric:got2000_gt27:-:*:*:*:*:*:*:*
    cpe:2.3:h:mitsubishielectric:got2000_gt27:-:*:*:*:*:*:*:*
  • cpe:2.3:o:mitsubishielectric:got2000_gt25_firmware:01.19.000:*:*:*:*:*:*:*
    cpe:2.3:o:mitsubishielectric:got2000_gt25_firmware:01.19.000:*:*:*:*:*:*:*
  • cpe:2.3:o:mitsubishielectric:got2000_gt25_firmware:01.39.010:*:*:*:*:*:*:*
    cpe:2.3:o:mitsubishielectric:got2000_gt25_firmware:01.39.010:*:*:*:*:*:*:*
  • cpe:2.3:h:mitsubishielectric:got2000_gt25:-:*:*:*:*:*:*:*
    cpe:2.3:h:mitsubishielectric:got2000_gt25:-:*:*:*:*:*:*:*
  • cpe:2.3:o:mitsubishielectric:got2000_gt23_firmware:01.19.000:*:*:*:*:*:*:*
    cpe:2.3:o:mitsubishielectric:got2000_gt23_firmware:01.19.000:*:*:*:*:*:*:*
  • cpe:2.3:o:mitsubishielectric:got2000_gt23_firmware:01.39.010:*:*:*:*:*:*:*
    cpe:2.3:o:mitsubishielectric:got2000_gt23_firmware:01.39.010:*:*:*:*:*:*:*
  • cpe:2.3:h:mitsubishielectric:got2000_gt23:-:*:*:*:*:*:*:*
    cpe:2.3:h:mitsubishielectric:got2000_gt23:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2021-20592: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...