FFmpeg 2.1 libavcodec/h264_refs.c build_def_list memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in FFmpeg 2.1. This affects the function build_def_list of the file libavcodec/h264_refs.c. Executing a manipulation can lead to memory corruption.
There is no exploit available.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability classified as critical was found in FFmpeg 2.1 (Multimedia Processing Software). This vulnerability affects the function build_def_list of the file libavcodec/h264_refs.c. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.
The issue has been introduced in 10/29/2013. The weakness was shared 11/27/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as h264_refs: make sure not to write over the bounds of the default ref list as confirmed git commit (GIT Repository). The advisory is shared for download at git.videolan.org. The vendor cooperated in the coordination of the public release. The exploitation appears 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 29 days. During that time the estimated underground price was around $0-$5k.
Applying the patch Patchwork [01/27] h264_refs: make sure not to write over the bounds of the default ref list is able to eliminate this problem. The bugfix is ready for download at patches.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 (100547†). The entries VDB-11403, VDB-11402, VDB-11401 and VDB-11400 are related to this item. 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: 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: Patchwork [01/27] h264_refs: make sure not to write over the bounds of the default ref list
Timeline
10/29/2013 🔍11/27/2013 🔍
11/27/2013 🔍
12/06/2013 🔍
04/17/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: h264_refs: make sure not to write over the bounds of the default ref list
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-11404
OSVDB: 100547
See also: 🔍
Entry
Created: 12/06/2013 14:32Updated: 04/17/2019 12:54
Changes: 12/06/2013 14:32 (52), 04/17/2019 12:54 (2)
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.