FFmpeg 2.0.1 Bounds-Check libavcodec/parser.c ff_combine_frame memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in FFmpeg 2.0.1 and classified as critical. Impacted is the function ff_combine_frame of the file libavcodec/parser.c of the component Bounds-Check Handler. The manipulation leads to memory corruption.
No exploit exists.
The affected component should be upgraded.
Details
A vulnerability was found in FFmpeg 2.0.1 (Multimedia Processing Software). It has been rated as critical. This issue affects the function ff_combine_frame of the file libavcodec/parser.c of the component Bounds-Check Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability.
The weakness was disclosed 09/26/2013 by Piotr Bandurski (ami_stuff) as avcodec/parser: reset indexes on realloc failure as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. The public release has been coordinated in cooperation with the project team. The attack needs to be done within the local network. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
Upgrading to version 2.1 eliminates this vulnerability. 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 (100500†) and Secunia (SA55802†). The entries VDB-11348, VDB-11349, VDB-11350 and VDB-11351 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- FFmpeg 2.0.1
- 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.6VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.6
VulDB Temp Score: 7.3
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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 2.1
Patch: git.videolan.org
Timeline
09/26/2013 🔍09/26/2013 🔍
11/29/2013 🔍
12/04/2013 🔍
04/17/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: avcodec/parser: reset indexes on realloc failure
Researcher: Piotr Bandurski (ami_stuff)
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-11357
Secunia: 55802 - FFmpeg Multiple Vulnerabilities, Moderately Critical
OSVDB: 100500
See also: 🔍
Entry
Created: 12/04/2013 13:46Updated: 04/17/2019 09:32
Changes: 12/04/2013 13:46 (55), 04/17/2019 09:32 (1)
Complete: 🔍
Committer: olku
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.