FFmpeg up to 1.2 libavcodec/bmv.c decode_bmv_frame Local Privilege Escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FFmpeg up to 1.2. It has been classified as problematic. Affected is the function decode_bmv_frame of the file libavcodec/bmv.c. The manipulation leads to an unknown weakness.
There is no available exploit.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in FFmpeg up to 1.2 (Multimedia Processing Software) and classified as problematic. This issue affects the function decode_bmv_frame of the file libavcodec/bmv.c. The impact remains unknown.
The weakness was presented 04/04/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as bmv: check for len being valid in bmv_decode_frame() as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. The public release was 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.videolan.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 (95362†). See VDB-9837, VDB-9836, VDB-9835 and VDB-9834 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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.videolan.org
Timeline
04/04/2013 🔍04/04/2013 🔍
08/06/2013 🔍
05/08/2018 🔍
Sources
Product: ffmpeg.orgAdvisory: bmv: check for len being valid in bmv_decode_frame()
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9833
OSVDB: 95362
See also: 🔍
Entry
Created: 08/06/2013 11:00Updated: 05/08/2018 08:59
Changes: 08/06/2013 11:00 (47), 05/08/2018 08:59 (1)
Complete: 🔍
Committer: olku
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.