Memory corruption via excessive RPZA block count
Published Jun 18, 2022 · Updated Apr 15, 2025
Out-of-bounds write in FFmpeg 2.0 allows context-dependent attackers to corrupt memory through a crafted RPZA video stream. In libavcodec/rpza.c, rpza_decode_stream trusts an encoded block count that can exceed the frame's remaining blocks, so decoding writes pixels beyond the allocated frame buffer. Processing attacker-controlled RPZA media is required; public records establish invalid writes but do not establish code execution or data disclosure.
Summary
What happened
Out-of-bounds write in FFmpeg 2.0 allows context-dependent attackers to corrupt memory through a crafted RPZA video stream. In libavcodec/rpza.c, rpza_decode_stream trusts an encoded block count that can exceed the frame's remaining blocks, so decoding writes pixels beyond the allocated frame buffer. Processing attacker-controlled RPZA media is required; public records establish invalid writes but do not establish code execution or data disclosure.
The record
- CVE
- CVE-2014-125017
- Published
- Jun 18, 2022
- Updated
- Apr 15, 2025
- Vendor
- FFmpeg
- Product
- FFmpeg
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- 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.
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