FFmpeg 2.0 Bitstream Input libavcodec/vcr1.c vcr1_decode_frame memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FFmpeg 2.0 and classified as critical. This affects the function vcr1_decode_frame of the file libavcodec/vcr1.c of the component Bitstream Input Handler. The manipulation results in memory corruption.
No exploit is available.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability classified as critical has been found in FFmpeg 2.0 (Multimedia Processing Software). Affected is the function vcr1_decode_frame of the file libavcodec/vcr1.c of the component Bitstream Input Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability.
The issue has been introduced in 07/11/2013. The weakness was published 10/22/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as avcodec/vcr1: Fix bitstream input size check as confirmed advisory (Website). The advisory is shared for download at git.videolan.org. The public release has been coordinated with the vendor. The exploitability is told to be difficult. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 103 days. During that time the estimated underground price was around $0-$5k.
Applying the patch avcodec/vcr1: Fix bitstream input size check is able to eliminate this problem. The bugfix is ready for download at git.videolan.org. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at OSVDB (98878†) and Secunia (SA55460†). Further details are available at git.videolan.org. Similar entry is available at VDB-10979. Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
License
Website
- Product: https://ffmpeg.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: avcodec/vcr1: Fix bitstream input size check
Timeline
07/11/2013 🔍10/22/2013 🔍
10/22/2013 🔍
10/24/2013 🔍
10/25/2013 🔍
04/16/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: avcodec/vcr1: Fix bitstream input size check
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10980
Secunia: 55460 - FFmpeg "vcr1_decode_frame()" Denial of Service Vulnerability, Moderately Critical
OSVDB: 98878
Misc.: 🔍
See also: 🔍
Entry
Created: 10/25/2013 10:17Updated: 04/16/2019 09:42
Changes: 10/25/2013 10:17 (58), 04/16/2019 09:42 (1)
Complete: 🔍
Committer:
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.