Media-processing interruption via unpadded Shorten buffer
Published Jun 19, 2022 · Updated Apr 15, 2025
Memory corruption in FFmpeg 2.0 allows remote attackers to interrupt media processing via a crafted Shorten audio bitstream. The shorten_decode_frame function allocates its internal bitstream buffer to max_framesize without FF_INPUT_BUFFER_PADDING_SIZE, permitting decoder reads beyond the allocation. No authentication is required, but a consuming application must decode the attacker-controlled stream; the published impact is limited to availability.
Summary
What happened
Memory corruption in FFmpeg 2.0 allows remote attackers to interrupt media processing via a crafted Shorten audio bitstream. The shorten_decode_frame function allocates its internal bitstream buffer to max_framesize without FF_INPUT_BUFFER_PADDING_SIZE, permitting decoder reads beyond the allocation. No authentication is required, but a consuming application must decode the attacker-controlled stream; the published impact is limited to availability.
The record
- CVE
- CVE-2014-125022
- Published
- Jun 19, 2022
- Updated
- Apr 15, 2025
- Vendor
- FFmpeg
- Product
- FFmpeg
- Classifications
- CWE-119, T1499.004
- Attack vector
- network
- 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.
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