Security Resilience

CVE-2023-23443

Memory Safety in Hihonor Magic Os ≤ 7.0.0.156

Published
29 December 2023
Modified
17 April 2025
Patch / advisory
CVSS Score v3.1 4.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:L
EPSS Score 0.0016 5th percentile
Risk Priority 31 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-23443 is a medium-severity Type Confusion (CWE-843) vulnerability in Hihonor Magic Os. Its CVSS base score is 4.6 (Medium).

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

EU & UK References

Vulnerability Data

Some Honor products are affected by type confusion vulnerability, successful exploitation could cause information leak.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

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.
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.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-51427Same product: Hihonor Magic Os
CVE-2023-51428Same product: Hihonor Magic Os
CVE-2023-51426Same product: Hihonor Magic Os
CVE-2023-6939Same vendor: Hihonor
CVE-2023-51429Same product: Hihonor Magic Os
CVE-2023-51434Same vendor: Hihonor
CVE-2023-23441Same vendor: Hihonor
CVE-2023-51432Same vendor: Hihonor
CVE-2026-17948Shared CWE-843
CVE-2026-78956Shared CWE-843

Affected Assets

hihonor
magic os
≤ 7.0.0.156

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)
  • V1.5.2
  • V15.3.5

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional weaknesses.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development can detect type-confusion vulnerabilities through fuzzing and static analysis.

prevents

Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.

prevents

A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; type confusion is a regular implementation defect that secure coding practice addresses, but the clause mandates a practice rather than a mechanism, leaving a nameable remainder.

finds

A.8.8's reach is disclosure-based: it finds type confusion where it surfaces as a published CVE in third-party components (the observed examples show CVEs do exist for this class), but misses first-party code entirely (that is A.8.29's domain) and the research-gap note indicates many type confusion instances are reported as 'memory corruption' rather than type confusion specifically, shrinking the disclosed share.

References