FFmpeg 4.0.1 libavcodec error_resilience.c AVI File input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in FFmpeg 4.0.1. This impacts an unknown function of the file error_resilience.c of the component libavcodec. The manipulation as part of AVI File results in input validation. This vulnerability is identified as CVE-2018-13304. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability was found in FFmpeg 4.0.1 (Multimedia Processing Software). It has been classified as problematic. Affected is an unknown code block of the file error_resilience.c of the component libavcodec. The manipulation as part of a AVI File leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on availability. CVE summarizes:
In libavcodec in FFmpeg 4.0.1, improper maintenance of the consistency between the context profile field and studio_profile in libavcodec may trigger an assertion failure while converting a crafted AVI file to MPEG4, leading to a denial of service, related to error_resilience.c, h263dec.c, and mpeg4videodec.c.
The bug was discovered 06/27/2018. The weakness was released 07/05/2018 (Website). The advisory is available at github.com. This vulnerability is traded as CVE-2018-13304 since 07/05/2018. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 8 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entries connected to this vulnerability are available at VDB-120427, VDB-120425, VDB-120424 and VDB-120423. If you want to get best quality of vulnerability data, you may have to visit 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.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
06/27/2018 🔍07/05/2018 🔍
07/05/2018 🔍
07/05/2018 🔍
07/05/2018 🔍
04/03/2023 🔍
Sources
Product: ffmpeg.orgAdvisory: bd27a9364ca274ca97f1df6d984e88a0700fb235
Status: Not defined
CVE: CVE-2018-13304 (🔍)
GCVE (CVE): GCVE-0-2018-13304
GCVE (VulDB): GCVE-100-120426
See also: 🔍
Entry
Created: 07/05/2018 23:18Updated: 04/03/2023 14:58
Changes: 07/05/2018 23:18 (59), 02/25/2020 21:18 (1), 04/03/2023 14:58 (4)
Complete: 🔍
Cache ID: 216::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.