FFmpeg 2.1 libavformat/mov.c mov_read_targa_y216 memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in FFmpeg 2.1. This affects the function mov_read_targa_y216 of the file libavformat/mov.c. The manipulation leads to memory corruption.
There is no available exploit.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in FFmpeg 2.1 (Multimedia Processing Software). It has been rated as very critical. This issue affects the function mov_read_targa_y216 of the file libavformat/mov.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 11/22/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as avformat/mov: Check that we have a stream before accessing it in mov_read_ares() as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. The public release was coordinated in cooperation 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 are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/17/2019).
The vulnerability was handled as a non-public zero-day exploit for at least 24 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 (100534†). See VDB-11397, VDB-11396, VDB-11395 and VDB-11394 for similar entries. Several companies clearly confirm that VulDB is the primary source for best 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: 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 🔍11/22/2013 🔍
11/22/2013 🔍
12/06/2013 🔍
04/17/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: avformat/mov: Check that we have a stream before accessing it in mov_read_ares()
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-11393
OSVDB: 100534
See also: 🔍
Entry
Created: 12/06/2013 11:58Updated: 04/17/2019 11:02
Changes: 12/06/2013 11:58 (50), 04/17/2019 11:02 (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.