FFmpeg 2.0 Header Parsing libavcodec/jpeg2000dec.c jpeg2000_read_main_headers SIZ 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 2.0. It has been classified as problematic. This issue affects the function jpeg2000_read_main_headers of the file libavcodec/jpeg2000dec.c of the component Header Parsing. The manipulation as part of SIZ leads to an unknown weakness.
There is not any exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in FFmpeg 2.0 (Multimedia Processing Software). It has been rated as problematic. This issue affects the function jpeg2000_read_main_headers of the file libavcodec/jpeg2000dec.c of the component Header Parsing. The manipulation as part of a SIZ leads to a unknown weakness. The impact remains unknown.
The issue has been introduced in 07/11/2013. The weakness was released 09/17/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as jpeg2000dec: Add more checks when parsing headers as confirmed git commit (GIT Repository). The advisory is shared at git.libav.org. The public release was coordinated 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 (97468†). Entries connected to this vulnerability are available at VDB-10425, VDB-10424, VDB-10423 and VDB-10422. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: jpeg2000dec: Add more checks when parsing headers
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10421
OSVDB: 97468
See also: 🔍
Entry
Created: 09/23/2013 17:20Updated: 04/15/2019 21:45
Changes: 09/23/2013 17:20 (53), 04/15/2019 21:45 (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.