FFmpeg 1.2.0 Jpeg2000Tile libavcodec/jpeg2000dec.c denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FFmpeg 1.2.0 and classified as problematic. This affects an unknown part of the file libavcodec/jpeg2000dec.c of the component Jpeg2000Tile Handler. The manipulation results in denial of service. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability was found in FFmpeg 1.2.0 (Multimedia Processing Software). It has been classified as problematic. Affected is an unknown code of the file libavcodec/jpeg2000dec.c of the component Jpeg2000Tile Handler. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability.
The issue has been introduced in 03/07/2013. The weakness was disclosed 06/06/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as not defined advisory (Website). The advisory is shared for download at ffmpeg.org. The public release has been coordinated in cooperation with the vendor. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, 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 (94170†) and Secunia (SA53766†). The entries VDB-5510, VDB-7875, VDB-7876 and VDB-7877 are pretty similar. Once again VulDB remains the best source for 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: Denial of serviceCWE: CWE-404
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-9132
Secunia: 53766 - FFmpeg Multiple Vulnerabilities, Moderately Critical
OSVDB: 94170
See also: 🔍
Entry
Created: 06/14/2013 10:25Updated: 04/15/2019 12:44
Changes: 06/14/2013 10:25 (58), 04/15/2019 12:44 (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.