Local denial of service via unreleased memory
Published Aug 11, 2025 · Updated Aug 11, 2025
Memory leak in applications_settings in OpenHarmony v5.0.3 through v5.0.3.x allows local users to interrupt service by exhausting memory. The component retains objects after their effective lifetime instead of releasing their memory, allowing repeated use to increase consumption. Low-privileged local access is required, and the documented consequence is availability loss without data disclosure or modification.
Summary
What happened
Memory leak in applications_settings in OpenHarmony v5.0.3 through v5.0.3.x allows local users to interrupt service by exhausting memory. The component retains objects after their effective lifetime instead of releasing their memory, allowing repeated use to increase consumption. Low-privileged local access is required, and the documented consequence is availability loss without data disclosure or modification.
The record
- CVE
- CVE-2025-24925
- Published
- Aug 11, 2025
- Updated
- Aug 11, 2025
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-401, T1499.004
- 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.
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