Multimedia player crash via released-pointer modification
Published Jan 2, 2024 · Updated Nov 14, 2024
Use-after-free in OpenHarmony 3.2.0 through 3.2.2 allows local users to crash the multimedia player by modifying a released pointer. OpenHarmony identifies the multimedia player as the locus but has not published the function or lifetime error that leaves the pointer reachable after release. Local execution is required, and the documented consequence is limited to interruption of multimedia playback rather than data disclosure or modification.
Summary
What happened
Use-after-free in OpenHarmony 3.2.0 through 3.2.2 allows local users to crash the multimedia player by modifying a released pointer. OpenHarmony identifies the multimedia player as the locus but has not published the function or lifetime error that leaves the pointer reachable after release. Local execution is required, and the documented consequence is limited to interruption of multimedia playback rather than data disclosure or modification.
The record
- CVE
- CVE-2023-49135
- Published
- Jan 2, 2024
- Updated
- Nov 14, 2024
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2024CVE publishedPublication date reported by the CVE source.
- Nov 14, 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.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