FFmpeg 2.0 libavcodec/h261dec.c h261_decode_mb Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in FFmpeg 2.0. The impacted element is the function h261_decode_mb of the file libavcodec/h261dec.c. The manipulation leads to Remote Code Execution.
No exploit is available.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in FFmpeg 2.0 (Multimedia Processing Software) and classified as critical. This issue affects the function h261_decode_mb of the file libavcodec/h261dec.c. The manipulation with an unknown input leads to a remote code execution vulnerability. Impacted is confidentiality, integrity, and availability.
The issue has been introduced in 07/11/2013. The weakness was published 08/16/2013 by Mateusz Jurczyk and Gynvael Coldwind as h261: check the mtype index as confirmed git commit (GIT Repository). It is possible to read the advisory at git.libav.org. The public release has been coordinated with the project team. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 36 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 0.8.9 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.libav.org. The best possible mitigation is suggested to be patching the affected component. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at OSVDB (96409†) and Secunia (SA54389†). git.videolan.org is providing further details. Similar entry is available at VDB-9994. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- FFmpeg
- Libav
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.1VulDB Meta Temp Score: 7.7
VulDB Base Score: 8.1
VulDB Temp Score: 7.7
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: Remote Code ExecutionCWE: Unknown
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: 🔍
Upgrade: FFmpeg 0.8.9
Patch: git.libav.org
Timeline
07/11/2013 🔍08/16/2013 🔍
08/16/2013 🔍
08/20/2013 🔍
08/22/2013 🔍
04/15/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: h261: check the mtype index
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9995
Secunia: 54389 - FFmpeg Two Vulnerabilities, Less Critical
OSVDB: 96409
Misc.: 🔍
See also: 🔍
Entry
Created: 08/22/2013 11:37Updated: 04/15/2019 17:01
Changes: 08/22/2013 11:37 (54), 04/15/2019 17:01 (1)
Complete: 🔍
Committer:
Cache ID: 216:A64:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.