Security Resilience

CVE-2023-52105

Huawei Harmonyos 4.0.0

Published
16 January 2024
Modified
21 November 2024
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:N/A:H
EPSS Score 0.0035 27th percentile
Risk Priority 57 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-52105 is a high-severity Improper Privilege Management (CWE-269) vulnerability in Huawei Harmonyos. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 27th 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-2 (Account Management) and AC-24 (Access Control Decisions) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The nearby module has a privilege escalation vulnerability. Successful exploitation of this vulnerability may affect availability.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-27895Same product: Huawei Harmonyos
CVE-2026-34860Same product: Huawei Harmonyos
CVE-2023-52114Same product: Huawei Harmonyos
CVE-2023-52367Same product: Huawei Harmonyos
CVE-2023-46759Same product: Huawei Harmonyos
CVE-2023-46755Same product: Huawei Harmonyos
CVE-2023-52375Same product: Huawei Harmonyos
CVE-2023-52099Same product: Huawei Harmonyos
CVE-2023-41311Same product: Huawei Harmonyos
CVE-2023-44118Same product: Huawei Harmonyos

Affected Assets

huawei
harmonyos
4.0.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Directly enforces approved authorizations for logical access, stopping unauthorized actors from reaching resources.

Account management directly governs assignment and tracking of privileges so proper implementation stops the weakness from being introduced.

Requiring explicit access-control decisions ensures privileges are evaluated rather than assumed or omitted.

Enforces flow-control policies that restrict information movement between subjects and objects.

Separation of duties constrains how privileges may be assigned, reducing the chance of overly broad actor control.

Least privilege is the direct countermeasure to improper privilege management; implementing it eliminates the root cause.

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.

blocks

A.5.1 only requires that an information security policy and topic-specific policies (including on access control) exist and are reviewed; it does not itself enforce, implement or act on any access restriction, so the weakness can still be exploited (per the owner's explicit rule that governance/dependency clauses score none on effect verbs).

blocks

A.5.15 directly mandates determining access requirements, defining/enforcing topic-specific access control policy, assigning rights/restrictions by entity/role, consistency with classification, need-to-know, privileged access restrictions, segregation, formal authorization, and dynamic rules — which stops most improper privilege management from being exploitable; bounded remainder is flawed implementation of those rules (e.g. incorrect mapping or enforcement bugs).

blocks

A.5.16's identity lifecycle (unique binding, timely disable/remove, no duplicates, oversight of shared/non-human) directly stops most improper access by ensuring the actor in an access decision is correctly identified and authorized; the bounded remainder is non-identity mechanisms in CWE-284 such as path traversal or CSRF that do not turn on actor identity at all.

blocks

A.5.18 directly governs the provisioning, review, modification and timely revocation of access rights (including for role changes, termination and privilege levels), which stops most improper privilege spheres from being exploitable even if the assignment flaw exists; the bounded remainder is flaws in the underlying enforcement mechanism itself (e.g. AC-3/A.8.3)

blocks

Defining and communicating authorization levels for each role limits the assignment of excessive or unnecessary privileges.

finds

Ongoing audits and performance reviews of suppliers detect and correct situations where access controls or privilege assignments are weaker than contractually required, limiting an attacker's ability to exploit improper access control in the supplier's environment.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-269, a class-level weakness. Rules are authored against its narrower children: CWE-250, CWE-266, CWE-267, CWE-268, CWE-270, CWE-274.
  • No fine-grained STIG row for CWE-284, a pillar-level weakness. Rules are authored against its narrower children: CWE-749, CWE-1220.

References