| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.25 |
Summary
A vulnerability has been found in FFmpeg 2.0 and classified as problematic. Affected by this issue is the function ff_init_buffer_info of the file utils.c. The manipulation leads to memory corruption.
This vulnerability is referenced as CVE-2014-125016. No exploit is available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in FFmpeg 2.0 (Multimedia Processing Software). It has been rated as problematic. This issue affects the function ff_init_buffer_info of the file utils.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 availability.
The issue has been introduced in 07/11/2013. The weakness was published 02/15/2014 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as avcodec/utils: set AVFrame format unconditional as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. The identification of this vulnerability is CVE-2014-125016. 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 vulnerability was handled as a non-public zero-day exploit for at least 219 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. The git commit contains the following remark:
frame->format = avctx->pix_fmt;
The vulnerability is also documented in the databases at X-Force (91209) and Secunia (SA56987†). Similar entries are available at VDB-12366 and VDB-12367. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 5.3VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.3
VulDB Temp Score: 4.6
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: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
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: 🔍
0-Day Time: 🔍
Patch: git.videolan.org
Timeline
07/11/2013 🔍02/15/2014 🔍
02/22/2014 🔍
06/17/2022 🔍
Sources
Product: ffmpeg.orgAdvisory: avcodec/utils: set AVFrame format unconditional
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
CVE: CVE-2014-125016 (🔍)
GCVE (CVE): GCVE-0-2014-125016
GCVE (VulDB): GCVE-100-12365
X-Force: 91209 - FFmpeg ff_init_buffer_info() denial of service, Medium Risk
Secunia: 56987 - FFmpeg Multiple Vulnerabilities, Moderately Critical
See also: 🔍
Entry
Created: 02/22/2014 20:04Updated: 06/17/2022 23:30
Changes: 02/22/2014 20:04 (47), 04/16/2019 11:54 (8), 06/17/2022 23:30 (3)
Complete: 🔍
Cache ID: 216:B80:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.