Cyber Resilience

CVE-2024-56451

Memory Safety in Huawei Harmonyos 5.0.0

Memory Safety
Published
08 January 2025
Modified
13 January 2025
Patch / advisory
View advisory
CVSS Score v3.1 7.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
EPSS Score 0.0011 1th percentile
Risk Priority 51 floored blend · peak EPSS

Summary

CVE-2024-56451 is a high-severity Integer Overflow to Buffer Overflow (CWE-680) vulnerability in Huawei Harmonyos. Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 1th 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-56451 is an integer overflow vulnerability (CWE-190, CWE-680) during glTF model loading in the 3D engine module of Huawei software. Published on January 8, 2025, it carries a CVSS v3.1 base score of 7.3 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H), rated as high severity.

A local attacker with low privileges can exploit this vulnerability with low attack complexity and no user interaction required. Successful exploitation may lead to high confidentiality impact through unauthorized access to sensitive data, low integrity impact, and high availability impact such as denial of service.

Huawei has issued a security bulletin detailing mitigations and patches for this vulnerability, available at https://consumer.huawei.com/en/support/bulletin/2025/1/.

EU & UK References

Vulnerability Data

Integer overflow vulnerability during glTF model loading in the 3D engine module Impact: Successful exploitation of this vulnerability may affect availability.

CWE(s)
CWE-680CWE-190

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-58107Same product: Huawei Harmonyos
CVE-2024-57956Same product: Huawei Harmonyos
CVE-2025-54623Same product: Huawei Harmonyos
CVE-2025-48910Same product: Huawei Harmonyos
CVE-2023-52115Same product: Huawei Harmonyos
CVE-2024-54105Same product: Huawei Harmonyos
CVE-2025-54635Same product: Huawei Harmonyos
CVE-2024-58108Same product: Huawei Harmonyos
CVE-2025-64314Same product: Huawei Harmonyos
CVE-2026-24930Same product: Huawei Harmonyos

Affected Assets

huawei
harmonyos
5.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.2.6

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and analysis (static, dynamic, fuzzing) finds integer-overflow-to-allocation defects before deployment.

SA-15 Development Process, Standards, and Tools partial match

Mandates documented development standards and tools that enforce secure coding rules against unsafe integer arithmetic.

SA-8 Security and Privacy Engineering Principles partial match

Requires engineering principles such as safe arithmetic and bounds-checked allocation that directly stop integer overflow during memory-size computation.

SI-10 Information Input Validation partial match

Validates untrusted size/offset inputs before they reach allocation calculations, structurally blocking the integer overflow path.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent integer-overflow flaws during development, but eliminating only this CWE covers only part of the broad control intent.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect integer-overflow-to-buffer-overflow conditions during development.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates practices that can catch integer overflows before deployment.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify safe integer handling and bounds checking.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage use of safe arithmetic libraries and overflow detection.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require prevention of integer overflows that lead to buffer overflows.

References