LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52369: Stack overflow vulnerability in the NFC module.Successful exploitation of this vulnerability may affect ser...

Stack overflow vulnerability in the NFC module.Successful exploitation of this vulnerability may affect service availability and integrity.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-52369 is a critical Huawei NFC module flaw affecting listed HarmonyOS and EMUI versions. Successful exploitation could disrupt service availability and compromise integrity. The sources do not identify affected device models, fixed build numbers, or active exploitation, so urgency should focus on identifying exposed Huawei fleets and applying official vendor updates.

Executive priority

Treat this as a high-priority mobile platform remediation item for Huawei fleets, especially where devices support operational, payment, identity, or access workflows. Do not assume active compromise from the provided sources.

Technical view

The CVE describes a stack overflow in Huawei's NFC module, categorized as CWE-787. CVSS 3.1 is 9.1 with network attack vector, low complexity, no privileges, and no user interaction, impacting integrity and availability but not confidentiality. Affected products listed are HarmonyOS 2.0.0 through 4.0.0 and EMUI 12.0.0 through 13.0.0.

Likely exposure

Exposure appears limited to Huawei devices running the listed HarmonyOS or EMUI versions. The bundle does not provide CPEs, device model lists, carrier variants, or exact vulnerable build ranges, so asset inventory must be matched against Huawei bulletin guidance.

Exploitation context

The provided KEV signal is false, and the cited bundle does not state active exploitation or public exploit availability. Risk remains high because the CVSS vector indicates unauthenticated, low-complexity exploitation with high integrity and availability impact.

Researcher notes

Evidence is sparse beyond the vendor description, affected OS versions, CWE, and CVSS vector. The NFC module context suggests mobile-device exposure, but the bundle does not describe prerequisites, reachable interfaces, proof-of-concept details, or patched builds.

Mitigation direction

  • Check Huawei's February 2024 security bulletins for affected models and fixed builds.
  • Apply official Huawei or HarmonyOS security updates when available for affected devices.
  • Prioritize listed HarmonyOS and EMUI versions in managed mobile fleets.
  • Review vendor guidance before relying on compensating controls.
  • Restrict use of affected devices in critical workflows until patch status is confirmed.

Validation and detection

  • Inventory Huawei devices and record HarmonyOS or EMUI version numbers.
  • Compare device versions with the affected versions in the CVE record.
  • Check Huawei bulletins for model-specific fixed build information.
  • Confirm updates installed successfully through device management or local settings.
  • Document devices with unavailable patches for risk acceptance or isolation decisions.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-52369 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H3.95.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2023-52369Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HuaweiHarmonyOS4.0.0, 3.1.0, 3.0.0, 2.1.0, 2.0.0unaffected
HuaweiEMUI13.0.0, 12.0.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.