Code execution via audio teardown use-after-free
Published Feb 17, 2023 · Updated Mar 19, 2025
Use-after-free in mpv 0.29.1 allows attackers to execute arbitrary code or crash the player through a crafted media file. A race during audio-output uninitialization in audio.c leaves the ao_c context available for use after it has been freed. Exploitation requires local user interaction with the crafted file and can compromise the user's process or terminate playback.
Summary
What happened
Use-after-free in mpv 0.29.1 allows attackers to execute arbitrary code or crash the player through a crafted media file. A race during audio-output uninitialization in audio.c leaves the ao_c context available for use after it has been freed. Exploitation requires local user interaction with the crafted file and can compromise the user's process or terminate playback.
The record
- CVE
- CVE-2020-19824
- Published
- Feb 17, 2023
- Updated
- Mar 19, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 17, 2023CVE publishedPublication date reported by the CVE source.
- Mar 19, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- mpv audio.c fuzz reproductionproof of concept · demonstrated
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