Process crash via signed parameter-set identifiers
Published Jun 18, 2022 · Updated Apr 15, 2025
Out-of-bounds write in FFmpeg 2.0 HEVC decoding allows attackers to crash the process with a crafted HEVC bitstream. The signed vps_id and sps_id fields in libavcodec/hevc.h overflow into negative values that drive out-of-array accesses. Processing attacker-supplied HEVC media is required; published impact is limited to availability, with no reported data disclosure or modification.
Summary
What happened
Out-of-bounds write in FFmpeg 2.0 HEVC decoding allows attackers to crash the process with a crafted HEVC bitstream. The signed vps_id and sps_id fields in libavcodec/hevc.h overflow into negative values that drive out-of-array accesses. Processing attacker-supplied HEVC media is required; published impact is limited to availability, with no reported data disclosure or modification.
The record
- CVE
- CVE-2014-125014
- Published
- Jun 18, 2022
- Updated
- Apr 15, 2025
- Vendor
- FFmpeg
- Product
- FFmpeg
- Classifications
- CWE-787, CWE-119, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 18, 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