CVE-2025-20011: Communication Dsoftbus has a memory leak vulnerability
First published: Tue Mar 04 2025(Updated: )
in OpenHarmony v5.0.2 and prior versions allow a local attacker case DOS through missing release of memory.
Credit: scy@openharmony.io
| Affected Software | Affected Version | How to fix |
|---|---|---|
| OpenHarmony | <5.0.2 | |
| >=4.1<=5.0.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-20011?
CVE-2025-20011 is considered a medium severity vulnerability due to increased risk of denial of service attacks.
How do I fix CVE-2025-20011?
To mitigate CVE-2025-20011, upgrade OpenHarmony to version 5.0.3 or later which includes the necessary memory management fixes.
Who is affected by CVE-2025-20011?
CVE-2025-20011 affects all users running OpenHarmony versions up to and including 5.0.2.
What type of attack does CVE-2025-20011 enable?
CVE-2025-20011 allows a local attacker to perform a denial of service (DoS) attack due to insufficient memory release.
Is CVE-2025-20011 likely to be exploited in the wild?
While not widely reported, CVE-2025-20011 has the potential to be exploited by a local attacker if left unaddressed.
- agent/title
- agent/weakness
- agent/references
- agent/first-publish-date
- agent/type
- agent/description
- agent/guess-ai
- agent/software-canonical-lookup
- agent/author
- agent/source
- agent/event
- agent/severity
- agent/softwarecombine
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/nvd-api
- source/NVD
- vendor/openharmony
- canonical/openharmony
- vendor/openatom