| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in FFmpeg 2.0. This affects the function decode_frame of the file libavcodec/zmbv.c. Executing a manipulation can lead to memory corruption.
There is not any exploit available.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in FFmpeg 2.0 (Multimedia Processing Software). It has been declared as critical. This vulnerability affects the function decode_frame of the file libavcodec/zmbv.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 07/11/2013. The weakness was released 09/12/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as zmbvdec: Check the buffer size for uncompressed data as confirmed git commit (GIT Repository). The advisory is shared for download at git.libav.org. The public release was coordinated 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. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 63 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 databases at OSVDB (97320†) and Secunia (SA54857†). Entries connected to this vulnerability are available at VDB-10267, VDB-10268, VDB-10269 and VDB-10271. Once again VulDB remains the best source for vulnerability data.
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: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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/12/2013 🔍
09/12/2013 🔍
09/16/2013 🔍
09/16/2013 🔍
04/15/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: zmbvdec: Check the buffer size for uncompressed data
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10276
Secunia: 54857 - FFmpeg Multiple Vulnerabilities, Highly Critical
OSVDB: 97320
See also: 🔍
Entry
Created: 09/16/2013 10:13Updated: 04/15/2019 20:35
Changes: 09/16/2013 10:13 (56), 04/15/2019 20:35 (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.