Ffmpeg/Libav 2.1/9.1.0 Leaf Table decrypt_init Local Privilege Escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Ffmpeg and Libav 2.1/9.1.0. This affects the function decrypt_init of the file decrypt_init of the component Leaf Table Handler. This manipulation causes an unknown weakness.
There is not any exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability has been found in Ffmpeg and Libav 2.1/9.1.0 (Multimedia Processing Software) and classified as problematic. Affected by this vulnerability is the function decrypt_init of the file decrypt_init of the component Leaf Table Handler. The impact remains unknown.
The weakness was released 11/04/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as omadec: Fix wrong number of array elements as confirmed advisory (Website). The public release was coordinated with the project team. Technical details are known, but no exploit is available.
Applying the patch omadec: Fix wrong number of array elements 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 (99483†). Additional details are provided at git.videolan.org. Entries connected to this vulnerability are available at VDB-11102, VDB-11100 and VDB-11099. 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: 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: omadec: Fix wrong number of array elements
Timeline
11/04/2013 🔍11/04/2013 🔍
11/08/2013 🔍
04/12/2019 🔍
Sources
Product: ffmpeg.orgResearcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-11101
OSVDB: 99483
Misc.: 🔍
See also: 🔍
Entry
Created: 11/08/2013 14:36Updated: 04/12/2019 15:02
Changes: 11/08/2013 14:36 (50), 04/12/2019 15:02 (1)
Complete: 🔍
Committer:
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.