EUVD-2025-208679
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Lifecycle Timeline
3Description
in OpenHarmony v5.1.0 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through out-of-bounds write. This vulnerability can be exploited only in restricted scenarios.
Analysis
An out-of-bounds write vulnerability in OpenHarmony v5.1.0 and earlier versions allows local attackers with limited privileges to achieve arbitrary code execution within pre-installed applications through memory corruption. The vulnerability, tracked as CVE-2025-41432 and assigned CVSS 5.5, exploits CWE-787 (out-of-bounds write) and is limited to restricted attack scenarios that require local access and low privilege levels. While not currently listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, the availability of vulnerability disclosure documentation and the nature of memory corruption bugs suggest heightened risk for motivated threat actors.
Technical Context
This vulnerability involves a classic buffer overflow condition classified under CWE-787 (out-of-bounds write), a memory corruption weakness that allows attackers to write data beyond allocated buffer boundaries. The affected product is OpenHarmony (cpe:2.3:a:openharmony:openharmony:*:*:*:*:*:*:*:*), an open-source operating system distributed by Huawei. The flaw resides in pre-installed applications running on the OpenHarmony platform, and exploitation requires the attacker to have local system access with user-level privileges. The out-of-bounds write condition likely corrupts the heap or stack memory used by system services, enabling code execution through techniques such as function pointer hijacking or return-oriented programming (ROP) chain construction.
Affected Products
OpenHarmony versions from v5.0.3 through v5.1.0.x are affected, as confirmed by the ENISA EUVD-2025-208679 vulnerability tracking entry. The vulnerability applies to the OpenHarmony operating system framework itself as identified by the CPE string cpe:2.3:a:openharmony:openharmony:*:*:*:*:*:*:*:*, meaning all product variants and implementations of OpenHarmony within the affected version range are susceptible. Organizations deploying OpenHarmony should consult the official OpenHarmony security disclosure at https://gitcode.com/openharmony/security/tree/master/zh/security-disclosure/2025/2025-10.md for vendor-specific guidance and confirmation of patch availability.
Remediation
Immediately upgrade to OpenHarmony v5.2.0 or later (exact patched version to be confirmed via vendor advisory at https://gitcode.com/openharmony/security/tree/master/zh/security-disclosure/2025/2025-10.md). For organizations unable to upgrade immediately, implement the following mitigations: restrict local system access and enforce the principle of least privilege for user accounts and applications; disable or isolate pre-installed applications not required for core functionality; apply SELinux or AppArmor mandatory access control policies to limit the blast radius of code execution; and monitor system logs for anomalous memory access patterns or unexpected process spawning. If devices are network-connected, segment them from critical infrastructure until patching is completed.
Priority Score
Share
External POC / Exploit Code
Leaving vuln.today