CVE Vulnerabilities

CVE-2021-22340

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Published: Jun 29, 2021 | Modified: Nov 21, 2024
CVSS 3.x
4.1
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
4.7 MEDIUM
AV:L/AC:M/Au:N/C:N/I:N/A:C
RedHat/V2
RedHat/V3
Ubuntu

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

Weakness

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Affected Software

Name Vendor Start Version End Version
Manageone Huawei 6.5.1-spc200 (including) 6.5.1-spc200 (including)
Manageone Huawei 8.0.0 (including) 8.0.0 (including)
Manageone Huawei 8.0.0-lcnd81 (including) 8.0.0-lcnd81 (including)
Manageone Huawei 8.0.0-rc2 (including) 8.0.0-rc2 (including)
Manageone Huawei 8.0.0-rc3 (including) 8.0.0-rc3 (including)
Manageone Huawei 8.0.0-rc3.spc100 (including) 8.0.0-rc3.spc100 (including)
Manageone Huawei 8.0.0-spc100 (including) 8.0.0-spc100 (including)
Manageone Huawei 8.0.1 (including) 8.0.1 (including)
Smc2.0 Huawei v600r019c10spc700 (including) v600r019c10spc700 (including)
Smc2.0 Huawei v600r019c10spc702 (including) v600r019c10spc702 (including)
Smc2.0 Huawei v600r019c10spc703 (including) v600r019c10spc703 (including)
Smc2.0 Huawei v600r019c10spc800 (including) v600r019c10spc800 (including)
Smc2.0 Huawei v600r019c10spc900 (including) v600r019c10spc900 (including)
Smc2.0 Huawei v600r019c10spc910 (including) v600r019c10spc910 (including)
Smc2.0 Huawei v600r019c10spc920 (including) v600r019c10spc920 (including)
Smc2.0 Huawei v600r019c10spc921 (including) v600r019c10spc921 (including)
Smc2.0 Huawei v600r019c10spc922 (including) v600r019c10spc922 (including)
Smc2.0 Huawei v600r019c10spc930 (including) v600r019c10spc930 (including)
Smc2.0 Huawei v600r019c10spc931 (including) v600r019c10spc931 (including)

Extended Description

A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:

A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.

Potential Mitigations

  • Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
  • Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

References