Decoder crash via unchecked allocation failure
Published Dec 16, 2022 · Updated Apr 16, 2025
NULL pointer dereference in FFmpeg before 5.1 allows remote attackers to crash a decoder via VP3 media under memory pressure. In vp3_decode_frame, libavcodec/vp3.c stores av_malloc's result in s->edge_emu_buffer and continues decoding without rejecting a NULL result. Exploitation requires VP3 input and allocation failure; the bounded consequence is termination of the decoding process, not data access or modification.
Summary
What happened
NULL pointer dereference in FFmpeg before 5.1 allows remote attackers to crash a decoder via VP3 media under memory pressure. In vp3_decode_frame, libavcodec/vp3.c stores av_malloc's result in s->edge_emu_buffer and continues decoding without rejecting a NULL result. Exploitation requires VP3 input and allocation failure; the bounded consequence is termination of the decoding process, not data access or modification.
The record
- CVE
- CVE-2022-3109
- Published
- Dec 16, 2022
- Updated
- Apr 16, 2025
- Vendor
- FFmpeg
- Product
- FFmpeg
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 16, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=FFmpeg 5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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