LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52378: Vulnerability of incorrect service logic in the WindowManagerServices module.Successful exploitation of thi...

Vulnerability of incorrect service logic in the WindowManagerServices module.Successful exploitation of this vulnerability may cause features to perform abnormally.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Huawei reports a critical logic flaw in the WindowManagerServices module affecting listed HarmonyOS and EMUI versions. The public description is brief, but the CVSS vector indicates possible remote, unauthenticated impact to confidentiality, integrity, and availability. Organizations with affected Huawei mobile or HarmonyOS devices should prioritize vendor bulletin review and patch verification.

Executive priority

High priority for organizations with Huawei-managed mobile or HarmonyOS fleets. The public detail is sparse, but the vendor severity and CVSS 9.8 score justify expedited inventory and patch confirmation, especially for devices accessing corporate data.

Technical view

CVE-2023-52378 is described as incorrect service logic in WindowManagerServices. Huawei says successful exploitation may cause features to perform abnormally. The record assigns CWE-693 and CVSS 3.1 score 9.8 with AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Public technical detail is limited.

Likely exposure

Exposure appears limited to Huawei HarmonyOS 3.1.0 and 3.0.0, and EMUI 13.0.0 as listed in the CVE source bundle. Asset owners should verify exact device OS versions and security patch levels against Huawei's February 2024 security bulletins.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, exploit publication, or proof-of-concept evidence. Treat exploitation status as unconfirmed. The high CVSS score reflects potential impact and ease characteristics in the CVE vector, not confirmed attacks.

Researcher notes

Public sources identify the vulnerable module and impact category but do not provide root-cause detail, attack prerequisites beyond CVSS, indicators, or exploit artifacts. CWE-693 suggests a protection-mechanism failure, but deeper analysis requires vendor patches, firmware diffs, or additional disclosure.

Mitigation direction

  • Review Huawei February 2024 security bulletins for affected build and update details.
  • Apply Huawei-provided security updates when the relevant device update is confirmed.
  • Prioritize managed fleets running HarmonyOS 3.1.0, HarmonyOS 3.0.0, or EMUI 13.0.0.
  • Use MDM controls to restrict unsupported or unpatched affected devices from sensitive access.
  • Monitor Huawei advisories for revised affected-version or remediation guidance.

Validation and detection

  • Inventory Huawei devices by OS family, version, build, and patch level.
  • Compare discovered versions with HarmonyOS 3.1.0, 3.0.0, and EMUI 13.0.0.
  • Confirm whether February 2024 Huawei security updates are installed.
  • Review endpoint or MDM telemetry for abnormal WindowManager or UI feature behavior.
  • Document exceptions where affected devices cannot be promptly updated.
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-693: 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-52378 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.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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
HuaweiHarmonyOS3.1.0, 3.0.0unaffected
HuaweiEMUI13.0.0unaffected
Weakness

CWE details

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

CWE-693 · source CWE mapping

Protection Mechanism Failure

Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.