Local code execution via liteos_a use-after-free
Published Aug 11, 2025 · Updated Aug 11, 2025
Use-after-free in OpenHarmony 5.0.3 through 5.0.3.x allows local users to execute arbitrary code in the trusted computing base. OpenHarmony identifies liteos_a and the trusted computing base as the locus, but has not disclosed the freed object, triggering operation, or faulty lifetime handling. A low-privileged local account is required, and successful exploitation crosses a security boundary to execute code and interrupt service without altering protected data.
Summary
What happened
Use-after-free in OpenHarmony 5.0.3 through 5.0.3.x allows local users to execute arbitrary code in the trusted computing base. OpenHarmony identifies liteos_a and the trusted computing base as the locus, but has not disclosed the freed object, triggering operation, or faulty lifetime handling. A low-privileged local account is required, and successful exploitation crosses a security boundary to execute code and interrupt service without altering protected data.
The record
- CVE
- CVE-2025-24298
- Published
- Aug 11, 2025
- Updated
- Aug 11, 2025
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2025CVE publishedPublication date reported by the CVE source.
- Aug 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=v5.0.3 <=v5.0.3.x
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.
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