CVE-2025-54623VulnerabilityPublished 6 Aug 2025

CVE-2025-54623: Huawei HarmonyOS · Integer Overflow to Buffer Overflow

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

6.3Medium

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

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

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

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

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Aug 2025
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-26.

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 =5.1.0 =5.0.1	Fixed in–

AI-suggested

1. Immediate inventory and assessment: Identify all Huawei devices running HarmonyOS versions 5.0.1 and 5.1.0 within the organization, focusing on those involved in device management and critical operations. 2. Network segmentation: Restrict network access to Huawei devices, especially the devicemanager module, limiting adjacent network exposure. Use VLANs and firewall rules to isolate these devices from untrusted or less secure network segments. 3. Monitor network traffic: Deploy intrusion detection/prevention systems (IDS/IPS) to detect anomalous traffic patterns indicative of exploitation attempts targeting the devicemanager module. 4. Apply vendor updates promptly: Although no patches are currently linked, maintain close monitoring of Huawei security advisories and apply updates as soon as patches become available. 5. Implement strict access controls: Enforce least privilege principles on device management interfaces and restrict administrative access to trusted personnel and systems. 6. Conduct penetration testing and vulnerability scanning: Regularly test the environment for signs of exploitation or presence of similar vulnerabilities. 7. Incident response preparedness: Develop and rehearse response plans for potential denial-of-service or compromise scenarios involving Huawei devices. 8. Collaborate with Huawei support: Engage with Huawei for guidance, early patch access, and coordinated vulnerability disclosure handling.

Description

Out-of-bounds read vulnerability in the devicemanager module. Impact: Successful exploitation of this vulnerability may affect availability.

Impact

For European organizations, the impact of this vulnerability depends largely on the extent of HarmonyOS deployment within their environments. HarmonyOS is primarily used in Huawei devices, including smartphones, IoT devices, and other smart hardware. Organizations using Huawei devices for critical operations, device management, or IoT infrastructure could face risks of service disruption due to availability impacts. The out-of-bounds read leading to buffer overflow could cause system crashes or denial of service, affecting operational continuity. Additionally, the partial compromise of confidentiality and integrity could expose sensitive device management data or allow manipulation of device states, which may have downstream effects on network security and data protection compliance. Given the medium severity and the lack of required privileges or user interaction, the vulnerability could be exploited by attackers with adjacent network access, such as within corporate LANs or via compromised devices on the same network segment. This elevates the risk in environments with dense Huawei device usage or interconnected IoT ecosystems. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits post-disclosure. European organizations must consider the potential for targeted attacks exploiting this vulnerability to disrupt services or gain footholds in device management systems.

CWE-680Integer Overflow to Buffer Overflow (opens in a new tab)
Compound weakness
The product performs a calculation to determine how much memory to allocate, but an integer overflow can occur that causes less memory to be allocated than expected, leading to a buffer overflow.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Overflow Buffers (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Filter Failure through Buffer Overflow (opens in a new tab)
Buffer Overflow via Symbolic Links (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

consumer.huawei.com/en/support/bulletin/2025/8/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Aug 2025, 02:36 UTC

WeaknessesCWE-680

Technical details

References

Community reviews

Related threats