FFmpeg 2.0 Frame Rate libavcodec/vp3.c theora_decode_header Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in FFmpeg 2.0. The affected element is the function theora_decode_header of the file libavcodec/vp3.c of the component Frame Rate Handler. Such manipulation leads to an unknown weakness.
No exploit exists.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in FFmpeg 2.0 (Multimedia Processing Software). It has been rated as problematic. Affected by this issue is the function theora_decode_header of the file libavcodec/vp3.c of the component Frame Rate Handler. The impact remains unknown.
The issue has been introduced in 07/11/2013. The weakness was disclosed 09/16/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as vp3: Check the framerate for validity as confirmed git commit (GIT Repository). The advisory is shared for download at git.libav.org. The public release has been coordinated in cooperation with the vendor. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 67 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.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 (97459†). The entries VDB-10416, VDB-10415, VDB-10414 and VDB-10413 are pretty similar. Once again VulDB remains the best source for vulnerability data.
Affected
- FFmpeg 2.0
- Libav 9.9
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.6VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
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: Remote Code ExecutionCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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/11/2013 🔍09/16/2013 🔍
09/16/2013 🔍
09/23/2013 🔍
04/15/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: vp3: Check the framerate for validity
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10412
OSVDB: 97459
See also: 🔍
Entry
Created: 09/23/2013 14:44Updated: 04/15/2019 20:58
Changes: 09/23/2013 14:44 (52), 04/15/2019 20:58 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.