Huawei 576up005 HOTA-CM-H-Shark-BD Headset out-of-bounds write

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Huawei 576up005 HOTA-CM-H-Shark-BD, 577HOTA-CM-H-Shark-BD, 581up-HOTA-CM-H-Shark-BD, 586-HOTA-CM-H-Shark-BD, 588-HOTA-CM-H-Shark-BD, 606-HOTA-CM-H-Shark-BD, BI-ACC-REPORT and CM-H-Shark-BD. This vulnerability affects unknown code of the component Headset Handler. The manipulation leads to out-of-bounds write. This vulnerability is documented as CVE-2020-36602. It is possible to launch the attack on the physical device. There is not any exploit available.
Details
A vulnerability was found in Huawei 576up005 HOTA-CM-H-Shark-BD, 577HOTA-CM-H-Shark-BD, 581up-HOTA-CM-H-Shark-BD, 586-HOTA-CM-H-Shark-BD, 588-HOTA-CM-H-Shark-BD, 606-HOTA-CM-H-Shark-BD, BI-ACC-REPORT and CM-H-Shark-BD (Reporting Software) and classified as critical. This issue affects some unknown processing of the component Headset Handler. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
There is an out-of-bounds read and write vulnerability in some headset products. An unauthenticated attacker gets the device physically and crafts malformed message with specific parameter and sends the message to the affected products. Due to insufficient validation of message, which may be exploited to cause out-of-bounds read and write.
The weakness was released 09/21/2022 as huawei-sa-20220826-01. The advisory is shared at huawei.com. The identification of this vulnerability is CVE-2020-36602 since 08/25/2022. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/28/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
- 576up005 HOTA-CM-H-Shark-BD
- 577HOTA-CM-H-Shark-BD
- 581up-HOTA-CM-H-Shark-BD
- 586-HOTA-CM-H-Shark-BD
- 588-HOTA-CM-H-Shark-BD
- 606-HOTA-CM-H-Shark-BD
- BI-ACC-REPORT
- CM-H-Shark-BD
License
Website
- Vendor: https://www.huawei.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/25/2022 🔍09/21/2022 🔍
09/21/2022 🔍
05/28/2025 🔍
Sources
Vendor: huawei.comAdvisory: huawei-sa-20220826-01
Status: Confirmed
CVE: CVE-2020-36602 (🔍)
GCVE (CVE): GCVE-0-2020-36602
GCVE (VulDB): GCVE-100-209201
Entry
Created: 09/21/2022 09:19Updated: 05/28/2025 18:52
Changes: 09/21/2022 09:19 (39), 10/21/2022 15:29 (11), 05/28/2025 18:52 (15)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.