CVE-2024-56446
Huawei Harmonyos 5.0.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LSummary
CVE-2024-56446 is a medium-severity Use of Uninitialized Variable (CWE-457) vulnerability in Huawei Harmonyos. Its CVSS base score is 4.0 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-56446 is a vulnerability involving variables not being initialized in the notification module of Huawei consumer products. Published on January 8, 2025, it carries a CVSS v3.1 base score of 4.0 (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) and maps to CWE-457 (Use of Uninitialized Variable) and CWE-908 (Use of Uninitialized Resource). Successful exploitation impacts availability.
A local attacker can exploit this vulnerability with low complexity, no required privileges, and no user interaction. Exploitation disrupts availability, potentially leading to denial-of-service conditions in the affected notification module.
Huawei has published a support bulletin at https://consumer.huawei.com/en/support/bulletin/2025/1/ addressing this issue, which security practitioners should consult for mitigation details and available patches.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-53155
Vulnerability Data
Vulnerability of variables not being initialized in the notification module Impact: Successful exploitation of this vulnerability may affect availability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis directly find uses of uninitialized variables before deployment.
Documented development standards and tools can enforce initialization requirements in code.
Engineering principles can mandate explicit variable initialization to avoid uninitialized use.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly catch uninitialized-variable defects via static analysis and code review while the control encompasses many additional development controls.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect uninitialized-variable bugs, but the control is broader.
Secure development life cycle mandates practices that reduce uninitialized-variable defects.
Application security requirements can specify initialization rules, but the control itself does not directly address the weakness.
Secure system architecture and engineering principles include defensive coding practices that prevent use of uninitialized memory or objects.
Secure coding explicitly requires variable initialization and static-analysis checks.