Service interruption via failed AC-3 encoder initialization
Published Jun 2, 2021 · Updated Aug 4, 2024
Memory leak in FFmpeg 4.2 allows remote attackers to interrupt service through crafted media processed by the AC-3 encoder. During ff_ac3_encode_init, validate_options can fail after DSP state allocation, but the error path returns without running init_fail cleanup. Processing the crafted input requires user interaction; repeated failed initialization consumes memory until the hosting process hangs or terminates.
Summary
What happened
Memory leak in FFmpeg 4.2 allows remote attackers to interrupt service through crafted media processed by the AC-3 encoder. During ff_ac3_encode_init, validate_options can fail after DSP state allocation, but the error path returns without running init_fail cleanup. Processing the crafted input requires user interaction; repeated failed initialization consumes memory until the hosting process hangs or terminates.
The record
- CVE
- CVE-2020-22046
- Published
- Jun 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
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
- FFmpeg AC-3 memory-leak reproducerproof of concept · unverified
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