FFmpeg up to 2.0 libavcodec/mlpdec.c read_restart_header Local Privilege Escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in FFmpeg up to 2.0. The affected element is the function read_restart_header of the file libavcodec/mlpdec.c. This manipulation causes an unknown weakness.
No exploit exists.
It is suggested to install a patch to address this issue.
Details
A vulnerability has been found in FFmpeg up to 2.0 (Multimedia Processing Software) and classified as problematic. Affected by this vulnerability is the function read_restart_header of the file libavcodec/mlpdec.c. The impact remains unknown.
The weakness was disclosed 07/12/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. The public release has been coordinated in cooperation with the project team. Technical details are known, but no exploit is available.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.libav.org. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (95168†). The entries VDB-9701, VDB-9700, VDB-9699 and VDB-9698 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- FFmpeg
- Libav
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: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Local Privilege EscalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
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.libav.org
Timeline
07/12/2013 🔍07/12/2013 🔍
07/24/2013 🔍
05/07/2018 🔍
Sources
Product: ffmpeg.orgAdvisory: git.videolan.org
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9697
OSVDB: 95168
See also: 🔍
Entry
Created: 07/24/2013 19:23Updated: 05/07/2018 09:13
Changes: 07/24/2013 19:23 (47), 05/07/2018 09:13 (1)
Complete: 🔍
Committer:
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.