Cyber Resilience

CVE-2023-52953

Path Traversal in Huawei Harmonyos 2.0.0 … 3.0.0

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

Summary

CVE-2023-52953 is a medium-severity Path Traversal (CWE-22) vulnerability in Huawei Harmonyos. Its CVSS base score is 6.2 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 20th 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 AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — 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-2023-52953 is a path traversal vulnerability (CWE-22) in the Medialibrary module. Successful exploitation affects integrity and confidentiality, with a CVSS v3.1 base score of 6.2 (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). The vulnerability was published on 2025-01-08.

A local attacker can exploit this vulnerability with low attack complexity, requiring no privileges or user interaction. Exploitation leads to high-impact disruption of availability, alongside effects on integrity and confidentiality as stated in the description.

The Huawei consumer support bulletin provides details on mitigation: https://consumer.huawei.com/en/support/bulletin/2025/1/.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Path traversal vulnerability in the Medialibrary module Impact: Successful exploitation of this vulnerability will affect integrity and confidentiality.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-41302Same product: Huawei Emui
CVE-2024-47292Same product: Huawei Emui
CVE-2023-52544Same product: Huawei Emui
CVE-2024-30417Same product: Huawei Emui
CVE-2024-45443Same product: Huawei Emui
CVE-2025-31174Same product: Huawei Harmonyos
CVE-2023-39407Same product: Huawei Harmonyos
CVE-2025-54653Same product: Huawei Harmonyos
CVE-2025-54652Same product: Huawei Harmonyos
CVE-2023-39401Same product: Huawei Emui

Affected Assets

huawei
emui
12.0.0, 13.0.0
huawei
harmonyos
2.0.0, 2.1.0, 3.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.3.2

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Input validation directly neutralizes special path elements before pathname construction occurs.

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

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-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

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 catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

mitigates

Information access restriction limits which files an application may read or write.

References