FFmpeg 2.1 libavcodec/h264.c execute_decode_slices Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in FFmpeg 2.1. Affected by this vulnerability is the function execute_decode_slices of the file libavcodec/h264.c. The manipulation results in an unknown weakness.
There is no available exploit.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability, which was classified as problematic, was found in FFmpeg 2.1 (Multimedia Processing Software). Affected is the function execute_decode_slices of the file libavcodec/h264.c. The impact remains unknown.
The issue has been introduced in 10/29/2013. The weakness was presented 01/06/2014 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as h264: check that execute_decode_slices() is not called too many times as confirmed git commit (GIT Repository). The advisory is shared for download at git.videolan.org. The public release was coordinated in cooperation with the vendor. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 69 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.videolan.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 (101833†). See VDB-11752, VDB-11751, VDB-11750 and VDB-11749 for similar entries. Once again VulDB remains the best source for vulnerability data.
Affected
- FFmpeg 2.1
- Libav 0.8.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: 5.6VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.6
VulDB Temp Score: 5.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: 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: 🔍
Patch: git.videolan.org
Timeline
10/29/2013 🔍01/06/2014 🔍
01/06/2014 🔍
01/08/2014 🔍
04/18/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: h264: check that execute_decode_slices() is not called too many times
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-11748
OSVDB: 101833
See also: 🔍
Entry
Created: 01/08/2014 17:05Updated: 04/18/2019 08:08
Changes: 01/08/2014 17:05 (51), 04/18/2019 08:08 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.