Adjacent code execution via DSoftBus use-after-free
Published Feb 2, 2024 · Updated Nov 8, 2024
Use-after-free in OpenHarmony DSoftBus 3.2.0 through 3.2.4 and 4.0.0 allows physically proximate attackers to execute code in applications. The vendor identifies communication_dsoftbus as the affected repository but has not disclosed the function, freed object, or input sequence that reuses it. Exploitation requires adjacent access and high-complexity conditions, needs no privileges or user interaction, and can cross application security boundaries.
Summary
What happened
Use-after-free in OpenHarmony DSoftBus 3.2.0 through 3.2.4 and 4.0.0 allows physically proximate attackers to execute code in applications. The vendor identifies communication_dsoftbus as the affected repository but has not disclosed the function, freed object, or input sequence that reuses it. Exploitation requires adjacent access and high-complexity conditions, needs no privileges or user interaction, and can cross application security boundaries.
The record
- CVE
- CVE-2024-21860
- Published
- Feb 2, 2024
- Updated
- Nov 8, 2024
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-416, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 2, 2024CVE publishedPublication date reported by the CVE source.
- Nov 8, 2024Record 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=v3.2.0 <=v3.2.4
- Affected versionversion=v4.0.0 <v4.0.1
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