FFmpeg 1.2.0 SOT Marker libavcodec/jpeg2000dec.c jpeg2000_read_main_headers Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FFmpeg 1.2.0. It has been classified as problematic. This vulnerability affects the function jpeg2000_read_main_headers of the file libavcodec/jpeg2000dec.c of the component SOT Marker Handler. This manipulation causes Remote Code Execution.
There is no available exploit.
Upgrading the affected component is recommended.
Details
A vulnerability was found in FFmpeg 1.2.0 (Multimedia Processing Software). It has been declared as problematic. Affected by this vulnerability is the function jpeg2000_read_main_headers of the file libavcodec/jpeg2000dec.c of the component SOT Marker Handler. The manipulation with an unknown input leads to a remote code execution vulnerability. As an impact it is known to affect confidentiality, integrity, and availability.
The issue has been introduced in 03/07/2013. The weakness was presented 06/06/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as not defined advisory (Website). The advisory is shared at ffmpeg.org. The public release was coordinated in cooperation with the project team. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 91 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.2.1 eliminates this vulnerability. The upgrade is hosted for download at git.videolan.org. Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.videolan.org. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at OSVDB (94171†) and Secunia (SA53766†). See VDB-5510, VDB-7875, VDB-7876 and VDB-7877 for similar entries. 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.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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: FFmpeg 1.2.1
Patch: git.videolan.org
Timeline
03/07/2013 🔍04/30/2013 🔍
06/06/2013 🔍
06/06/2013 🔍
06/14/2013 🔍
06/19/2013 🔍
04/15/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: ffmpeg.org
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9133
Secunia: 53766 - FFmpeg Multiple Vulnerabilities, Moderately Critical
OSVDB: 94171
See also: 🔍
Entry
Created: 06/14/2013 10:25Updated: 04/15/2019 12:52
Changes: 06/14/2013 10:25 (58), 04/15/2019 12:52 (1)
Complete: 🔍
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.