There is an out-of-bounds read and write vulnerability in some headset products.
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Sep 20, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 18th percentile
- CWE
- CWE-125
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| huawei | 576up005 hota-cm-h-shark-bd firmware | cpe:2.3:o:huawei:576up005_hota-cm-h-shark-bd_firmware |
| huawei | 576up005 hota-cm-h-shark-bd | cpe:2.3:h:huawei:576up005_hota-cm-h-shark-bd |
| huawei | 577hota-cm-h-shark-bd firmware | cpe:2.3:o:huawei:577hota-cm-h-shark-bd_firmware |
| huawei | 577hota-cm-h-shark-bd | cpe:2.3:h:huawei:577hota-cm-h-shark-bd |
| huawei | 581up-hota-cm-h-shark-bd firmware | cpe:2.3:o:huawei:581up-hota-cm-h-shark-bd_firmware |
| huawei | 581up-hota-cm-h-shark-bd | cpe:2.3:h:huawei:581up-hota-cm-h-shark-bd |
| huawei | 586-hota-cm-h-shark-bd firmware | cpe:2.3:o:huawei:586-hota-cm-h-shark-bd_firmware |
| huawei | 586-hota-cm-h-shark-bd | cpe:2.3:h:huawei:586-hota-cm-h-shark-bd |
| huawei | 588-hota-cm-h-shark-bd firmware | cpe:2.3:o:huawei:588-hota-cm-h-shark-bd_firmware |
| huawei | 588-hota-cm-h-shark-bd | cpe:2.3:h:huawei:588-hota-cm-h-shark-bd |
| huawei | 606-hota-cm-h-shark-bd firmware | cpe:2.3:o:huawei:606-hota-cm-h-shark-bd_firmware |
| huawei | 606-hota-cm-h-shark-bd | cpe:2.3:h:huawei:606-hota-cm-h-shark-bd |
and 4 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- huawei 576up005 hota-cm-h-shark-bd firmware1.0.0.576
- huawei 577hota-cm-h-shark-bd firmware1.0.0.577
- huawei 581up-hota-cm-h-shark-bd firmware1.0.0.581
- huawei 586-hota-cm-h-shark-bd firmware1.0.0.586
- huawei 588-hota-cm-h-shark-bd firmware1.0.0.588
- huawei 606-hota-cm-h-shark-bd firmware1.0.0.606
- huawei bi-acc-report firmware1.0.0.1
- huawei bi-acc-report firmware1.0.0.2
- huawei bi-acc-report firmware1.0.0.3
- huawei bi-acc-report firmware1.0.0.4
- huawei bi-acc-report firmware1.0.0.5
- huawei cm-h-shark-bd firmware1.0.0.106
- huawei cm-h-shark-bd firmware1.0.0.116
- huawei cm-h-shark-bd firmware1.0.0.202
- huawei cm-h-shark-bd firmware1.0.0.208
- huawei cm-h-shark-bd firmware1.0.0.216
- huawei cm-h-shark-bd firmware1.0.0.226
- huawei cm-h-shark-bd firmware1.0.0.228
- huawei cm-h-shark-bd firmware1.0.0.510
- huawei cm-h-shark-bd firmware1.0.0.520
Versions reported by the vendor
Affected version ranges reported by the assigning authority (huawei). Independent of NVD's CPE analysis and usually ahead of it.
n/a 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
- 1.0.0.576-fullpackage, 1.0.0.577-fullpackage, 1.0.0.581-fullpackage, 1.0.0.586-fullpackage, 1.0.0.588-fullpackage, 1.0.0.606-fullpackage, 1.0.0.1,1.0.0.2,1.0.0.3,1.0.0.4,1.0.0.5, 1.0.0.106,1.0.0.116,1.0.0.202,1.0.0.208,1.0.0.216,1.0.0.226,1.0.0.228,1.0.0.510,1.0.0.520,1.0.0.522,1.0.0.566,1.0.0.576,1.0.0.578,1.0.0.586,1.0.0.588,1.0.0.66(VN2-SP11),1.0.0.66(VN2-SP15),1.0.0.66(VN2affected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.