FFmpeg 2.0 libavcodec/svq3.c svq3_decode_mb Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in FFmpeg 2.0 and classified as problematic. Impacted is the function svq3_decode_mb of the file libavcodec/svq3.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, which was classified as problematic, has been found in FFmpeg 2.0 (Multimedia Processing Software). This issue affects the function svq3_decode_mb of the file libavcodec/svq3.c. The impact remains unknown.
The issue has been introduced in 07/11/2013. The weakness was presented 09/17/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as svq3: Check for any negative return value from ff_h264_check_intra_pred_mode as confirmed git commit (GIT Repository). The advisory is shared at git.libav.org. The public release was coordinated in cooperation with the project team. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 68 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 (97480†). See VDB-10435, VDB-10434, VDB-10432 and VDB-10431 for similar entries. Several companies clearly confirm that VulDB is the primary source for best 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/17/2013 🔍
09/17/2013 🔍
09/23/2013 🔍
04/15/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: svq3: Check for any negative return value from ff_h264_check_intra_pred_mode
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10433
OSVDB: 97480
See also: 🔍
Entry
Created: 09/23/2013 17:37Updated: 04/15/2019 22:54
Changes: 09/23/2013 17:37 (51), 04/15/2019 22:54 (1)
Complete: 🔍
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.