FFmpeg 2.0 Invalid Bits-Per-Coded-Sample libavformat/xwma.c xwma_read_header denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FFmpeg 2.0. It has been rated as problematic. Impacted is the function xwma_read_header of the file libavformat/xwma.c of the component Invalid Bits-Per-Coded-Sample Handler. Performing a manipulation results in denial of service.
There is not any exploit available.
It is suggested to install a patch to address this issue.
Details
A vulnerability classified as critical has been found in FFmpeg 2.0 (Multimedia Processing Software). This affects the function xwma_read_header of the file libavformat/xwma.c of the component Invalid Bits-Per-Coded-Sample 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 07/11/2013. The weakness was released 09/29/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as xwma: Avoid division by zero as confirmed git commit (GIT Repository). The advisory is shared at git.libav.org. The public release was coordinated with the project team. The exploitability is told to be easy. 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 80 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 (97904†). Entries connected to this vulnerability are available at VDB-10523, VDB-10522, VDB-10520 and VDB-10519. 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: 7.5VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
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: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: git.libav.org
Timeline
07/11/2013 🔍09/29/2013 🔍
09/29/2013 🔍
10/01/2013 🔍
04/16/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: xwma: Avoid division by zero
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10521
OSVDB: 97904
See also: 🔍
Entry
Created: 10/01/2013 15:03Updated: 04/16/2019 09:07
Changes: 10/01/2013 15:03 (52), 04/16/2019 09:07 (2)
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.