Memory corruption via stale H.264 bit contexts
Published Jun 19, 2022 · Updated Apr 15, 2025
Use-after-free in FFmpeg 2.0 H.264 decoding allows attackers to corrupt memory via crafted partitioned video data. The decoder carries data_partitioning state between decode calls, causing GetBitContext objects to reference data freed after an earlier packet. Exploitation requires affected H.264 input to traverse multiple decode calls; the invalid access can crash or corrupt the decoding process.
Summary
What happened
Use-after-free in FFmpeg 2.0 H.264 decoding allows attackers to corrupt memory via crafted partitioned video data. The decoder carries data_partitioning state between decode calls, causing GetBitContext objects to reference data freed after an earlier packet. Exploitation requires affected H.264 input to traverse multiple decode calls; the invalid access can crash or corrupt the decoding process.
The record
- CVE
- CVE-2014-125020
- Published
- Jun 19, 2022
- Updated
- Apr 15, 2025
- Vendor
- FFmpeg
- Product
- FFmpeg
- Classifications
- CWE-119, CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 19, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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=2.0
What conditions does exploitation require?
What is affected?
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