cve.bz

CVE-2021-22340 huawei: Race Condition

4.1 mediumEPSS 0.1%

Medium (4.1) in huawei. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
There is a multiple threads race condition vulnerability in Huawei product. A race condition exists for concurrent I/O read by multiple threads. An attacker with the root permission can exploit this vulnerability by performing some operations. Successful exploitation of this vulnerability may cause the system to crash. Affected product versions include: ManageOne 6.5.1.SPC200, 8.0.0,8.0.0-LCND81, 8.0.0.SPC100, 8.0.1,8.0.RC2, 8.0.RC3, 8.0.RC3.SPC100;SMC2.0 V600R019C10SPC700,V600R019C10SPC702, V600R019C10SPC703,V600R019C10SPC800, V600R019C10SPC900, V600R019C10SPC910, V600R019C10SPC920, V600R019C10SPC921, V600R019C10SPC922, V600R019C10SPC930, V600R019C10SPC931

Severity

CVSS 3.1

4.1 medium
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-22340 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-22340?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-22340?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-22340 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
huawei:manageone6.5.1:spc200
huawei:manageone8.0.0
huawei:manageone8.0.0:lcnd81
huawei:manageone8.0.0:rc2
huawei:manageone8.0.0:rc3
huawei:manageone8.0.0:rc3.spc100
huawei:manageone8.0.0:spc100
huawei:manageone8.0.1
huawei:smc2.0v600r019c10spc700
huawei:smc2.0v600r019c10spc702
huawei:smc2.0v600r019c10spc703
huawei:smc2.0v600r019c10spc800
huawei:smc2.0v600r019c10spc900
huawei:smc2.0v600r019c10spc910
huawei:smc2.0v600r019c10spc920
huawei:smc2.0v600r019c10spc921
huawei:smc2.0v600r019c10spc922
huawei:smc2.0v600r019c10spc930
huawei:smc2.0v600r019c10spc931

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON