LiveActive security incident?Get immediate response
CVE Record

CVE-2021-22340: There is a multiple threads race condition vulnerability in Huawei product.

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-22340 is a race condition in Huawei ManageOne and SMC2.0. A user who already has root permission could trigger concurrent I/O behavior that may crash the system. The main business risk is availability disruption in affected Huawei management or conferencing environments, not initial compromise.

Executive priority

Treat as a targeted availability risk for affected Huawei platforms. It is not evidenced as internet-exploited, but systems that manage critical operations should be reviewed and remediated through Huawei guidance.

Technical view

The CVE describes a multiple-thread race condition during concurrent I/O reads. Exploitation requires root permission and unspecified operations. Successful exploitation may cause a system crash. The bundle lists affected ManageOne and SMC2.0 versions, but provides no CVSS score, CWE, exploit detail, or confirmed fixed versions.

Likely exposure

Exposure is limited to organizations running the listed Huawei ManageOne or SMC2.0 versions. Risk is higher where many administrators have root access or privileged accounts are weakly controlled.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked KEV. The attacker already needs root permission, so this is primarily a post-compromise or malicious-admin availability risk.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or fixed-version details are included in the provided bundle. The root-permission prerequisite materially limits attack paths, but the crash impact matters for operationally important deployments.

Mitigation direction

  • Check Huawei PSIRT guidance for applicable updates or vendor-approved mitigations.
  • Inventory ManageOne and SMC2.0 deployments against the listed affected versions.
  • Restrict and review root access on affected systems.
  • Prioritize remediation for systems supporting critical operations or shared services.
  • Monitor affected platforms for unexpected crashes or availability degradation.

Validation and detection

  • Confirm exact Huawei product names and versions in asset inventory.
  • Compare installed versions with the affected ManageOne and SMC2.0 release lists.
  • Review privileged account assignments and recent root-level activity.
  • Check operational logs for unexplained crashes on affected systems.
  • Document whether Huawei guidance has been applied or scheduled.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-22340 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aManageOne;SMC2.06.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, V600R019C10SPC700,V600R019C10SPC702,V600R019C10SPC703,V600R019C10SPC800,V600R019C10SPC900,V600R019C10SPC910,V600R019C10SPC920,V600R019C10SPC921,V600R019C10SPC922,V600R019C10SPC930,V600R019C10SPC931Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.