Denial of service via FIFO memory leak
Published Jun 1, 2021 · Updated Aug 4, 2024
Denial of service in FFmpeg 4.2 allows remote attackers to exhaust memory through crafted media that a user opens. The fifo_alloc_common function in libavutil/fifo.c fails to release allocated FIFO memory while processing malformed input. Exploitation requires user interaction, and repeated leaked allocations can exhaust memory and interrupt the FFmpeg process.
Summary
What happened
Denial of service in FFmpeg 4.2 allows remote attackers to exhaust memory through crafted media that a user opens. The fifo_alloc_common function in libavutil/fifo.c fails to release allocated FIFO memory while processing malformed input. Exploitation requires user interaction, and repeated leaked allocations can exhaust memory and interrupt the FFmpeg process.
The record
- CVE
- CVE-2020-22043
- Published
- Jun 1, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 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
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