FFmpeg 1.2.0 nreslevels2decode libavcodec/jpeg2000.c ff_jpeg2000_init_component denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in FFmpeg 1.2.0. Affected is the function ff_jpeg2000_init_component of the file libavcodec/jpeg2000.c of the component nreslevels2decode Handler. Performing a manipulation results in denial of service.
There is no exploit available.
It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in FFmpeg 1.2.0 (Multimedia Processing Software). This affects the function ff_jpeg2000_init_component of the file libavcodec/jpeg2000.c of the component nreslevels2decode 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 shared 06/05/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as not defined advisory (Website). The advisory is shared at ffmpeg.org. The vendor cooperated in the coordination of the public release. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 90 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 (94167†) and Secunia (SA53766†). The entries VDB-5510, VDB-7875, VDB-7876 and VDB-7877 are related to this item. Several companies clearly confirm that VulDB is the primary source for best 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/05/2013 🔍
06/05/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-9129
Secunia: 53766 - FFmpeg Multiple Vulnerabilities, Moderately Critical
OSVDB: 94167
See also: 🔍
Entry
Created: 06/14/2013 10:23Updated: 04/15/2019 12:32
Changes: 06/14/2013 10:23 (59), 04/15/2019 12:32 (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.