CVE-2023-52714
Huawei Harmonyos 2.0.0 … 4.0.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-52714 is a high-severity Violation of Secure Design Principles (CWE-657) vulnerability in Huawei Harmonyos. Its CVSS base score is 7.5 (High).
Operationally, ranked at the 26th 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-5 (Separation of Duties) and AC-6 (Least Privilege) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-57338
Vulnerability Data
Vulnerability of defects introduced in the design process in the hwnff module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Explicitly requires application of security and privacy engineering principles throughout the lifecycle, structurally preventing their violation.
Separation of duties is a core secure design principle whose mandated implementation directly stops the violation from occurring.
Least privilege is a fundamental secure design principle whose enforcement prevents the violation from being introduced.
Mandates separation of user and system functionality, a classic secure design principle that stops the violation at design time.
Requires isolation of security functions, directly preventing violation of that established design principle.
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.5.8 mandates integrating secure design risk assessment, requirements derivation (including from threat modelling), and periodic review into the project life cycle, which stops many violations of secure design principles from reaching production; it leaves a bounded remainder (post-design implementation or coding errors not caught by project-level reviews).
A.8.25 mandates secure design and secure-SDLC practices (requirements, checkpoints, secure coding, testing per 8.28/8.29) that directly implement well-established secure design principles, so the violation cannot be exploited in well-implemented cases; the bounded remainder is outsourced development where assurance (8.30) may not be obtained or non-mandated principles outside the org's chosen methodology.
A.8.27 mandates establishing, documenting, and applying secure design/engineering principles (security by design, least privilege, default deny, fail securely, assume breach, zero trust, distrust external input, hardening, design review against attack patterns) directly to prevent violations of those principles in the resulting system; the bounded remainder is that a flawed implementation of the principles (or their incomplete application to outsourced development) can still allow the violation to arise and be exploitable.
Secure coding practices help realize secure design principles at implementation time.
Security testing can detect violations of secure design principles before release.
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.