Cyber Resilience

CVE-2024-56436

Huawei Harmonyos 5.0.0

Published
08 January 2025
Modified
27 September 2025
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS Score 0.0019 8th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2024-56436 is a medium-severity Improper Restriction of Rendered UI Layers or Frames (CWE-1021) vulnerability in Huawei Harmonyos. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

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-56436 is a cross-process screen stack vulnerability in the UIExtension module. It carries a CVSS v3.1 base score of 5.5 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) and is linked to CWE-1021 (as well as NVD-CWE-noinfo). Successful exploitation may affect service confidentiality.

A local attacker with no privileges required can exploit this vulnerability through low-complexity attacks that necessitate user interaction. Upon success, the attacker achieves high confidentiality impact, enabling unauthorized access to sensitive data across processes without affecting integrity or availability.

Huawei has published a security bulletin with further details at https://consumer.huawei.com/en/support/bulletin/2025/1/.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Cross-process screen stack vulnerability in the UIExtension module Impact: Successful exploitation of this vulnerability may affect service confidentiality.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
T1056 Input Capture Collection
Adversaries may use methods of capturing user input to obtain credentials or collect information.
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-54110Same product: Huawei Harmonyos
CVE-2024-54112Same product: Huawei Harmonyos
CVE-2024-56435Same product: Huawei Harmonyos
CVE-2025-54607Same product: Huawei Harmonyos
CVE-2024-12602Same product: Huawei Harmonyos
CVE-2024-56445Same product: Huawei Harmonyos
CVE-2025-48909Same product: Huawei Harmonyos
CVE-2025-53169Same product: Huawei Harmonyos
CVE-2025-46590Same product: Huawei Harmonyos
CVE-2024-56439Same product: Huawei Harmonyos

Affected Assets

huawei
harmonyos
5.0.0

Mitigating Controls

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 require implementing frame-ancestors / X-Frame-Options controls that prevent this weakness.

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.

finds

Security testing can detect missing frame protections, but does not itself implement the control.

degrades

Web filtering can block or sandbox untrusted frames, but does not enforce application-level frame-busting or CSP.

prevents

Application security requirements can mandate frame-ancestors / X-Frame-Options, directly addressing UI redressing risks.

prevents

Secure architecture principles include isolation of UI layers and proper use of browser security controls.

prevents

Secure coding practices directly require implementation of frame-busting headers or CSP frame-ancestors directives.

References