| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in FFmpeg 2.0. The affected element is the function hls_decode_entry of the file libavcodec/hevc.c. The manipulation leads to memory corruption.
There is no available exploit.
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 hls_decode_entry of the file libavcodec/hevc.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 presented 02/06/2014 by Gynvael Coldwind and Mateusz Jurczyk (j00ru) with Google as avcodec/hevc: hls_decode_entry: check that the previous slice segment is available... as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. 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 210 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. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (91073), SecurityFocus (BID 65504†) and Secunia (SA56838†). See VDB-12294, VDB-12295, VDB-12296 and VDB-12297 for similar entries. 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
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.videolan.org
Timeline
07/11/2013 🔍02/06/2014 🔍
02/06/2014 🔍
02/07/2014 🔍
02/14/2014 🔍
04/16/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: avcodec/hevc: hls_decode_entry: check that the previous slice segment is available...
Researcher: Gynvael Coldwind, Mateusz Jurczyk (j00ru)
Organization: Google
Status: Confirmed
GCVE (VulDB): GCVE-100-12293
X-Force: 91073 - FFmpeg hls_decode_entry() denial of service, Medium Risk
SecurityFocus: 65504 - FFmpeg Multiple Denial of Service Vulnerabilities
Secunia: 56838 - FFmpeg Multiple Vulnerabilities, Moderately Critical
See also: 🔍
Entry
Created: 02/14/2014 09:17Updated: 04/16/2019 10:38
Changes: 02/14/2014 09:17 (57), 04/16/2019 10:38 (3)
Complete: 🔍
Cache ID: 216:325: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.