FFmpeg 2.0 Packet Data libavformat/avidec.c read_gab2_sub memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in FFmpeg 2.0. The affected element is the function read_gab2_sub of the file libavformat/avidec.c of the component Packet Data Handler. Executing a manipulation can lead to memory corruption.
No exploit exists.
A patch should be applied to remediate this issue.
Details
A vulnerability classified as very critical was found in FFmpeg 2.0 (Multimedia Processing Software). This vulnerability affects the function read_gab2_sub of the file libavformat/avidec.c of the component Packet Data Handler. 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 07/11/2013. The weakness was disclosed 09/29/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as avidec: Make sure a packet is large enough before reading its data as confirmed git commit (GIT Repository). The advisory is available at git.libav.org. The public release has been coordinated in cooperation with the vendor. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful 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/16/2019).
The vulnerability was handled as a non-public zero-day exploit for at least 80 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.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 (97929†). The entries VDB-10523, VDB-10521, VDB-10520 and VDB-10519 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- FFmpeg 2.0
- Libav 9.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.libav.org
Timeline
07/11/2013 🔍09/29/2013 🔍
09/29/2013 🔍
10/01/2013 🔍
04/16/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: avidec: Make sure a packet is large enough before reading its data
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10522
OSVDB: 97929
See also: 🔍
Entry
Created: 10/01/2013 15:03Updated: 04/16/2019 09:11
Changes: 10/01/2013 15:03 (52), 04/16/2019 09:11 (2)
Complete: 🔍
Cache ID: 216:7EC: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.