FFmpeg 2.0 Error ff_vc1_decode_init_alloc_tables denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FFmpeg 2.0. It has been rated as problematic. This issue affects the function ff_vc1_decode_init_alloc_tables of the file ff_vc1_decode_init_alloc_tables of the component Error Handler. This manipulation causes denial of service.
No exploit is available.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in FFmpeg 2.0 (Multimedia Processing Software). It has been declared as critical. Affected by this vulnerability is the function ff_vc1_decode_init_alloc_tables of the file ff_vc1_decode_init_alloc_tables of the component Error Handler. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability.
The issue has been introduced in 07/11/2013. The weakness was published 09/22/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as vc1dec: Fix leaks in ff_vc1_decode_init_alloc_tables on errors as confirmed git commit (GIT Repository). The advisory is shared at git.libav.org. The public release has been coordinated with the project team. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 73 days. During that time the estimated underground price was around $0-$5k.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.libav.org. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (97643†). Similar entries are available at VDB-10468, VDB-10467, VDB-10466 and VDB-10464. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- FFmpeg 2.0
- Libav 9.9
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: 7.5VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
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: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: git.libav.org
Timeline
07/11/2013 🔍09/22/2013 🔍
09/22/2013 🔍
09/25/2013 🔍
04/16/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: vc1dec: Fix leaks in ff_vc1_decode_init_alloc_tables on errors
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10465
OSVDB: 97643
See also: 🔍
Entry
Created: 09/25/2013 10:24Updated: 04/16/2019 00:10
Changes: 09/25/2013 10:24 (52), 04/16/2019 00:10 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.