Service interruption via leaked file options
Published May 25, 2021 · Updated Aug 4, 2024
A memory leak in FFmpeg 4.2 allows attackers to exhaust process memory and interrupt service through failed file-option parsing. The open_files function returns after parse_optgroup fails without calling uninit_options on the allocated per-file options, leaving those allocations unreleased. Exploitation requires an application to repeatedly submit failing option groups; the upstream patch does not establish a direct network protocol.
Summary
What happened
A memory leak in FFmpeg 4.2 allows attackers to exhaust process memory and interrupt service through failed file-option parsing. The open_files function returns after parse_optgroup fails without calling uninit_options on the allocated per-file options, leaving those allocations unreleased. Exploitation requires an application to repeatedly submit failing option groups; the upstream patch does not establish a direct network protocol.
The record
- CVE
- CVE-2020-20451
- Published
- May 25, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 25, 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