CVE-2021-22321 Vulnerability Analysis & Exploit Details

CVE-2021-22321
Vulnerability Scoring

5.3
/10
Significant Risk

Security assessments indicate that CVE-2021-22321 presents a notable risk, potentially requiring prompt mitigation.

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-22321 Details

Status: Modified

Last updated: 🕠 21 Nov 2024, 05:49 UTC
Originally published on: 🕗 22 Mar 2021, 20:15 UTC

Time between publication and last update: 1339 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:L

CVE-2021-22321 Vulnerability Summary

CVE-2021-22321: There is a use-after-free vulnerability in a Huawei product. A module cannot deal with specific operations in special scenarios. Attackers can exploit this vulnerability by performing malicious operations. This can cause memory use-after-free, compromising normal service. Affected product include some versions of NIP6300, NIP6600, NIP6800, S1700, S2700, S5700, S6700 , S7700, S9700, Secospace USG6300, Secospace USG6500, Secospace USG6600 and USG9500.

Assessing the Risk of CVE-2021-22321

Access Complexity Graph

The exploitability of CVE-2021-22321 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-22321

With low attack complexity and no required privileges, CVE-2021-22321 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-22321, 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-22321, 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-22321 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2021-22321 poses no threat to data integrity.
  • Availability: Low
    CVE-2021-22321 may slightly degrade system performance without fully affecting service availability.

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 0.092% (probability of exploit)

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

CVE-2021-22321 References

External References

CWE Common Weakness Enumeration

CWE-416

Vulnerable Configurations

  • cpe:2.3:o:huawei:nip6300_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6300_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6300_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6300_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:nip6300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:nip6300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6600_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6600_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:nip6600:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:nip6600:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:nip6800_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:nip6800_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:nip6800:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:nip6800:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r007c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r007c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r007c01b102:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r007c01b102:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r011c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r011c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s12700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s12700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s12700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s12700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s1700_firmware:v200r009c00spc200:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s1700_firmware:v200r009c00spc200:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s1700_firmware:v200r009c00spc500:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s1700_firmware:v200r009c00spc500:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s1700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s1700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s1700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s1700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s1700_firmware:v200r011c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s1700_firmware:v200r011c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s1700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s1700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s1700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s1700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s1700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s1700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r011c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r011c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s2700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s2700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s2700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s2700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r011c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r011c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r011c10spc100:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r011c10spc100:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s5700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s5700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r011c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r011c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r011c10spc100:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r011c10spc100:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s6700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s6700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r011c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r011c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s7700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s7700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r007c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r007c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r007c01b102:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r007c01b102:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r008c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r008c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r010c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r010c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r010c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r011c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r011c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r011c00spc100:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r011c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r011c10:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:s9700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:s9700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:secospace_usg6300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_usg6300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:secospace_usg6500:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_usg6500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:secospace_usg6600_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:secospace_usg6600:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:secospace_usg6600:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:usg9500_firmware:v500r001c30:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:usg9500_firmware:v500r001c30:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:usg9500_firmware:v500r001c60:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:usg9500_firmware:v500r001c60:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:usg9500:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:usg9500:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2021-22321: 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-2130 – A vulnerability was found in OpenXE up to 1.12. It has been declared as problematic. This vulnerability affects unknown code of the component Ticke...
  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • 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...