Local code execution via out-of-bounds write
Published Mar 4, 2025 · Updated Mar 11, 2025
Out-of-bounds write in OpenHarmony 4.1.0 through 5.0.2 allows local users to execute code in pre-installed apps. The flaw is in Arkcompiler ETS Runtime, but OpenHarmony has not disclosed the affected function, malformed input, or unchecked memory-write operation. Local users need low privileges, no user interaction, and an undisclosed restricted scenario to reach the pre-installed application context.
Summary
What happened
Out-of-bounds write in OpenHarmony 4.1.0 through 5.0.2 allows local users to execute code in pre-installed apps. The flaw is in Arkcompiler ETS Runtime, but OpenHarmony has not disclosed the affected function, malformed input, or unchecked memory-write operation. Local users need low privileges, no user interaction, and an undisclosed restricted scenario to reach the pre-installed application context.
The record
- CVE
- CVE-2025-23240
- Published
- Mar 4, 2025
- Updated
- Mar 11, 2025
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 4, 2025CVE publishedPublication date reported by the CVE source.
- Mar 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v4.1.0 <=v5.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo