Cyber Resilience

CVE-2023-52360

Huawei Harmonyos 2.0.0 … 4.0.0

Published
18 February 2024
Modified
17 March 2025
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0029 22th percentile
Risk Priority 56 floored blend · peak EPSS

Summary

CVE-2023-52360 is a high-severity Logic/Time Bomb (CWE-511) vulnerability in Huawei Harmonyos. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data Destruction (T1485); ranked at the 22th 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 SI-7 (Software, Firmware, and Information Integrity) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Logic vulnerabilities in the baseband.Successful exploitation of this vulnerability may affect service integrity.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1485 Data Destruction Impact
Adversaries may destroy data and files on specific systems or in large numbers on a network to interrupt availability to systems, services, and network resources.
T1485.001 Lifecycle-Triggered Deletion Impact
Adversaries may modify the lifecycle policies of a cloud storage bucket to destroy all objects stored within.
T1489 Service Stop Impact
Adversaries may stop or disable services on a system to render those services unavailable to legitimate users.
T1490 Inhibit System Recovery Impact
Adversaries may delete or remove built-in data and turn off services designed to aid in the recovery of a corrupted system to prevent recovery.
T1491 Defacement Impact
Adversaries may modify visual content available internally or externally to an enterprise network, thus affecting the integrity of the original content.
T1529 System Shutdown/Reboot Impact
Adversaries may shutdown/reboot systems to interrupt access to, or aid in the destruction of, those systems.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-44099Same product: Huawei Emui
CVE-2024-47290Same product: Huawei Emui
CVE-2023-1695Same product: Huawei Emui
CVE-2026-28542Same product: Huawei Emui
CVE-2023-34164Same product: Huawei Emui
CVE-2023-52371Same product: Huawei Emui
CVE-2023-39397Same product: Huawei Emui
CVE-2023-41304Same product: Huawei Emui
CVE-2023-46765Same product: Huawei Emui
CVE-2026-24918Same product: Huawei Emui

Affected Assets

huawei
emui
12.0.0
huawei
harmonyos
2.0.0, 2.1.0, 4.0.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover hidden time- or logic-triggered code before deployment.

Integrity verification tools detect unauthorized code insertions that implement logic or time bombs.

Configuration change control and approval gates reduce the chance of covert malicious code being added.

Developer configuration management enforces controlled, auditable changes that hinder hidden bomb insertion.

Requires documented development standards and tools that can structurally exclude insertion of triggered malicious logic.

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 development practices directly reduce insertion of intentional trigger logic during coding.

DE.AE-02 partial match
prevents

Event analysis helps understand bomb-triggered disruption after it occurs.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect activation of time/logic conditions.

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 in development and acceptance can uncover hidden logic/time bombs before release.

A.8.15 Logging partial match
finds

Logging can record execution of time- or logic-triggered code, aiding detection after the fact.

finds

Monitoring activities may detect anomalous behavior triggered by a logic/time bomb.

prevents

Secure development lifecycle processes include code review and testing that detect logic/time bombs before deployment.

prevents

Secure coding standards and peer review directly prevent insertion of malicious time- or logic-triggered code.

prevents

Change management reviews reduce the chance of unauthorized malicious code insertion.

References