Process denial of service via leaked AVIOContext
Published Jun 1, 2021 · Updated Aug 4, 2024
Memory leak in FFmpeg 4.2 allows remote attackers to exhaust process memory by inducing user processing of media with the NUT muxer. The NUT trailer writer allocates a dynamic AVIOContext when no index entries exist, then bypasses the block that writes and releases the buffer. Exploitation requires user interaction with crafted media and can interrupt only the FFmpeg process through memory exhaustion.
Summary
What happened
Memory leak in FFmpeg 4.2 allows remote attackers to exhaust process memory by inducing user processing of media with the NUT muxer. The NUT trailer writer allocates a dynamic AVIOContext when no index entries exist, then bypasses the block that writes and releases the buffer. Exploitation requires user interaction with crafted media and can interrupt only the FFmpeg process through memory exhaustion.
The record
- CVE
- CVE-2020-22044
- Published
- Jun 1, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- 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
- FFmpeg ticket 8295 exploit referenceproof 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