FFmpeg 2.1 libavcodec/hevc.c hls_slice_header null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in FFmpeg 2.1. This affects the function hls_slice_header of the file libavcodec/hevc.c. The manipulation leads to null pointer dereference.
Additionally, an exploit exists.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, has been found in FFmpeg 2.1 (Multimedia Processing Software). This issue affects the function hls_slice_header of the file libavcodec/hevc.c. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability.
The issue has been introduced in 10/29/2013. The weakness was released 01/13/2014 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as avcodec/hevc: Check entry point arrays for malloc failure as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. The public release was coordinated with the project team. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a private exploit are known.
It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 76 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 (90548) and OSVDB (102156†). Entries connected to this vulnerability are available at VDB-11983, VDB-11982, VDB-11980 and VDB-11979. 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: 7.5VulDB Meta Temp Score: 6.7
VulDB Base Score: 7.5
VulDB Temp Score: 6.7
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: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Private
Status: Proof-of-Concept
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
10/29/2013 🔍01/13/2014 🔍
01/13/2014 🔍
01/17/2014 🔍
04/18/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: avcodec/hevc: Check entry point arrays for malloc failure
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-11981
X-Force: 90548
OSVDB: 102156
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 01/17/2014 09:04Updated: 04/18/2019 09:58
Changes: 01/17/2014 09:04 (52), 04/18/2019 09:58 (2)
Complete: 🔍
Cache ID: 216::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.