# CVE-2020-36602: Memory corruption in 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

> An attacker with physical access can exploit insufficient message validation in Huawei headsets to cause out-of-bounds read and write, potentially leading to code execution or denial of service.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2022
- **Updated:** 28 May 2025
- **Also known as:** GHSA-cq9m-rh8p-vchf

## What is CVE-2020-36602?

CVE-2020-36602 is a medium-severity memory corruption vulnerability in 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, published on 20 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2020-36602?

It affects 8 products.


Products: Huawei 576up005 Hota-Cm-H-Shark-Bd Firmware, Huawei 577hota-Cm-H-Shark-Bd Firmware, Huawei 581up-Hota-Cm-H-Shark-Bd Firmware, Huawei 586-Hota-Cm-H-Shark-Bd Firmware, Huawei 588-Hota-Cm-H-Shark-Bd Firmware, Huawei 606-Hota-Cm-H-Shark-Bd Firmware, Huawei Bi-Acc-Report Firmware, Huawei Cm-H-Shark-Bd Firmware.

## How do I fix CVE-2020-36602?

No fix has been published for CVE-2020-36602 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-36602 being exploited?

There is no known exploitation of CVE-2020-36602 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36602 and fix it if it is affected.

What it is: CVE-2020-36602 is a medium-severity memory corruption vulnerability in 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, published on 20 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36602 in the wild and no public exploit code.

Affected product: 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. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-36602/ (Markdown: https://insights.sbomify.com/CVE-2020-36602/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-36602
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-36602
- OSV: https://osv.dev/vulnerability/CVE-2020-36602

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-36602/
Summaries are generated and may contain mistakes; the official description above is the record.