CVE-2023-52104VulnerabilityPublished 16 Jan 2024Updated 2 Jun 2025

CVE-2023-52104: Huawei HarmonyOS · Improper Access Control

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Huawei HarmonyOS	Affected =4.0.0 =3.1.0 =3.0.0	Fixed in–

AI-suggested

Given the absence of official patches, European organizations should implement several specific measures: 1) Inventory and assess all Huawei HarmonyOS devices within their environment, focusing on versions 3.0.0, 3.1.0, and 4.0.0. 2) Restrict network access to these devices, especially limiting exposure of the WMS module or related services to untrusted networks. 3) Employ network segmentation and firewall rules to isolate vulnerable devices from critical systems. 4) Monitor network traffic for unusual or unauthorized access attempts targeting HarmonyOS devices, using anomaly detection and intrusion detection systems tailored to detect exploitation attempts of improper access control vulnerabilities. 5) Engage with Huawei support channels to obtain updates or patches as they become available and prioritize timely deployment. 6) Implement strict device usage policies, including disabling unnecessary services or features on HarmonyOS devices that could be exploited. 7) Educate IT and security teams about this vulnerability to enhance incident response readiness. These targeted steps go beyond generic advice by focusing on device-specific controls, network-level protections, and proactive monitoring tailored to the vulnerability's characteristics.

Description

Vulnerability of parameters being not verified in the WMS module. Successful exploitation of this vulnerability may affect service confidentiality.

Impact

For European organizations, the impact of CVE-2023-52104 depends largely on the presence and use of Huawei HarmonyOS devices within their infrastructure or supply chains. While HarmonyOS is primarily deployed on Huawei devices, its adoption in Europe is growing, especially in consumer electronics and IoT devices. The confidentiality breach risk could expose sensitive corporate or personal data handled by these devices, potentially leading to data leaks or espionage. Enterprises relying on Huawei smart devices for critical operations or connected environments may face increased risks of unauthorized data access. Additionally, sectors with stringent data protection requirements, such as finance, healthcare, and government, could be particularly vulnerable to confidentiality compromises. The lack of requirement for authentication or user interaction increases the risk of automated or remote exploitation, which could facilitate large-scale attacks if the vulnerability is weaponized. However, the absence of known exploits in the wild currently limits immediate risk, though proactive mitigation is advised.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 16:25 UTC

Technical details

References

Community reviews

Related threats