Service interruption via unreleased DSoftBus memory
Published Mar 4, 2025 · Updated Mar 4, 2025
Memory leak in DSoftBus in OpenHarmony 4.1.0 through 5.0.2 allows local users to interrupt service by exhausting memory. The OpenHarmony advisory identifies missing memory release in the communication subsystem but does not disclose the affected function, allocation path, or triggering input. Low-privileged local access is required, and the documented consequence is limited to availability loss.
Summary
What happened
Memory leak in DSoftBus in OpenHarmony 4.1.0 through 5.0.2 allows local users to interrupt service by exhausting memory. The OpenHarmony advisory identifies missing memory release in the communication subsystem but does not disclose the affected function, allocation path, or triggering input. Low-privileged local access is required, and the documented consequence is limited to availability loss.
The record
- CVE
- CVE-2025-20011
- Published
- Mar 4, 2025
- Updated
- Mar 4, 2025
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 4, 2025CVE publishedPublication date reported by the CVE source.
- Mar 4, 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