FFmpeg 2.1 libavcodec/h264.c ff_h264_check_intra_pred_mode memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in FFmpeg 2.1. This impacts the function ff_h264_check_intra_pred_mode of the file libavcodec/h264.c. Such manipulation leads to memory corruption.
There is no available exploit.
A patch should be applied to remediate this issue.
Details
A vulnerability, which was classified as very critical, has been found in FFmpeg 2.1 (Multimedia Processing Software). Affected by this issue is the function ff_h264_check_intra_pred_mode of the file libavcodec/h264.c. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability.
The issue has been introduced in 10/29/2013. The weakness was presented 01/18/2014 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as h264: limit allowed pred modes in ff_h264_check_intra_pred_mode() to 3 as confirmed git commit (GIT Repository). The advisory is available at git.videolan.org. The public release was coordinated in cooperation with the vendor. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 04/18/2019).
The vulnerability was handled as a non-public zero-day exploit for at least 81 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 (102675†). See VDB-12102, VDB-12101, VDB-12100 and VDB-12099 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.
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: 10.0VulDB Meta Temp Score: 9.5
VulDB Base Score: 10.0
VulDB Temp Score: 9.5
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: 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/18/2014 🔍
01/18/2014 🔍
01/31/2014 🔍
04/18/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: h264: limit allowed pred modes in ff_h264_check_intra_pred_mode() to 3
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-12098
OSVDB: 102675
See also: 🔍
Entry
Created: 01/31/2014 10:03Updated: 04/18/2019 10:51
Changes: 01/31/2014 10:03 (50), 04/18/2019 10:51 (2)
Complete: 🔍
Cache ID: 216:446:103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.