Vendor
2,424 published CVES affecting Huawei, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
Newest publication first · page 1 of 40 · showing the latest 1,000
Permission control vulnerability in the Bluetooth module. Impact: Successful exploitation of this vulnerability may affect availability.
Permission control vulnerability in the autofill service module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.
Permission control vulnerability in the Optimizer module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.
DoS vulnerability in the DSoftBus module. Impact: Successful exploitation of this vulnerability may affect availability.
DoS vulnerability in the DSoftBus module. Impact: Successful exploitation of this vulnerability may affect availability.
Permission control vulnerability in the event notification management module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.
DoS vulnerability in the window module. Impact: Successful exploitation of this vulnerability may affect availability.
OOB read vulnerability in the peripheral module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.
UAF vulnerability in the location service module. Impact: Successful exploitation of this vulnerability may affect availability.
Race condition vulnerability in the location service module. Impact: Successful exploitation of this vulnerability may affect availability.
Permission control vulnerability in the WLAN module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.
DoS vulnerability in the file parsing module. Impact: Successful exploitation of this vulnerability may affect availability.
Buffer overflow vulnerability in the file preview module. Impact: Successful exploitation of this vulnerability may affect availability.
Null pointer dereference vulnerability in the ArkWeb module. Impact: Successful exploitation of this vulnerability may affect availability.
Permission control vulnerability in the background task management module. Impact: Successful exploitation of this vulnerability may affect service integrity.
DoS vulnerability in the file parsing module. Impact: Successful exploitation of this vulnerability may affect availability.
Permission control vulnerability in the graphics module. Impact: Successful exploitation of this vulnerability may affect confidentiality.
The openUBMC device-management process parses PLDM-over-MCTP and NCSI-over-MCTP responses from on-bus devices, and three response parsers in the shared transport libraries subtract a fixed header or reserved-field size from a device-supplied response length without a lower-bound...
openUBMC assigns the full privilege set to pseudo-identities representing SNMP callers. An authenticated, but low-privilege, SNMP user can therefore invoke mapped backend operations as an administrative identity. In route_mapper/account.lua, get_user_privilege returns the complet...
Huawei's openUBMC ships a default SNMPv3 USM key that uses one value for both authentication and privacy. An attacker who holds the key (recoverable from the open-source build) can authenticate SNMPv3 to, and decrypt SNMPv3 traffic from, any unit that still carries the shipped ke...
Out-of-bounds read vulnerability in the graphics module. Successful exploitation of this vulnerability may affect availability.
Permission control vulnerability in the app lock module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.
Permission control vulnerability in the Settings module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.
Permission control vulnerability in the app management module. Impact: Successful exploitation of this vulnerability may affect availability.
DoS vulnerability in the input device module. Impact: Successful exploitation of this vulnerability may affect availability.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.