Service interruption via leaked encoder context
Published Jun 1, 2021 · Updated Aug 4, 2024
Memory leak in FFmpeg 4.2 allows context-dependent attackers to interrupt service during encoding of a crafted media file. ff_frame_thread_encoder_init allocates a per-thread AVCodecContext but fails to free it when option copying or initialization exits through the error path. Processing attacker-supplied media with user interaction can repeatedly consume memory until the FFmpeg process or its host loses availability.
Summary
What happened
Memory leak in FFmpeg 4.2 allows context-dependent attackers to interrupt service during encoding of a crafted media file. ff_frame_thread_encoder_init allocates a per-thread AVCodecContext but fails to free it when option copying or initialization exits through the error path. Processing attacker-supplied media with user interaction can repeatedly consume memory until the FFmpeg process or its host loses availability.
The record
- CVE
- CVE-2020-22037
- Published
- Jun 1, 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 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
- PoC_option158.jpgproof 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