FFmpeg 2.0 libavcodec/dnxhdenc.c dnxhd_init_rc memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in FFmpeg 2.0. This issue affects the function dnxhd_init_rc of the file libavcodec/dnxhdenc.c. The manipulation results in memory corruption.
This vulnerability was named CVE-2014-125002. There is no available exploit.
It is advisable to implement a patch to correct this issue.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Details
A vulnerability was found in FFmpeg 2.0 (Multimedia Processing Software). It has been classified as problematic. Affected is the function dnxhd_init_rc of the file libavcodec/dnxhdenc.c. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability.
The issue has been introduced in 07/11/2013. The weakness was presented 01/17/2014 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as dnxhdenc: fix mb_rc size as confirmed git commit (GIT Repository). The advisory is shared for download at git.videolan.org. This vulnerability is traded as CVE-2014-125002. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 190 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 vulnerability is also documented in the databases at X-Force (91661) and Secunia (SA57282†). See VDB-12582, VDB-12583, VDB-12584 and VDB-12586 for similar entries. VulDB is the best source for vulnerability data and more expert information about this specific topic.
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 🔍01/17/2014 🔍
03/07/2014 🔍
03/13/2014 🔍
06/17/2022 🔍
Sources
Product: ffmpeg.orgAdvisory: dnxhdenc: fix mb_rc size
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
CVE: CVE-2014-125002 (🔍)
GCVE (CVE): GCVE-0-2014-125002
GCVE (VulDB): GCVE-100-12588
X-Force: 91661 - FFmpeg dnxhd_init_rc() denial of service, Medium Risk
Secunia: 57282 - FFmpeg Multiple Vulnerabilities, Less Critical
See also: 🔍
Entry
Created: 03/13/2014 03:24 PMUpdated: 06/17/2022 11:16 PM
Changes: 03/13/2014 03:24 PM (46), 04/17/2019 09:04 AM (9), 06/17/2022 11:16 PM (3)
Complete: 🔍
Cache ID: 18:920:40
No comments yet. Languages: en.
Please log in to comment.