FFmpeg up to 2.0 libavcodec/vc1dec.c vc1_mc_1mv/vc1_mc_4mv_luma/ vc1_mc_4mv_chroma 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 up to 2.0. This affects the function vc1_mc_1mv/vc1_mc_4mv_luma/ vc1_mc_4mv_chroma of the file libavcodec/vc1dec.c. Performing a manipulation results in an unknown weakness.
No exploit exists.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in FFmpeg up to 2.0 (Multimedia Processing Software). It has been classified as problematic. This affects the function vc1_mc_1mv/vc1_mc_4mv_luma/ vc1_mc_4mv_chroma of the file libavcodec/vc1dec.c. The impact remains unknown.
The weakness was disclosed 08/05/2013 by Mateusz Jurczyk and Gynvael Coldwind 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 (96055†). 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
08/05/2013 🔍08/05/2013 🔍
08/12/2013 🔍
05/08/2018 🔍
Sources
Product: ffmpeg.orgAdvisory: git.videolan.org
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9897
OSVDB: 96055
Entry
Created: 08/12/2013 14:56Updated: 05/08/2018 09:00
Changes: 08/12/2013 14:56 (44), 05/08/2018 09:00 (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.