FFmpeg 2.0 APE Demuxer libavformat/ape.c ape_read_header Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in FFmpeg 2.0. The impacted element is the function ape_read_header of the file libavformat/ape.c of the component APE Demuxer. Performing a manipulation results in an unknown weakness.
There is no 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 classified as problematic. This affects the function ape_read_header of the file libavformat/ape.c of the component APE Demuxer. The impact remains unknown.
The issue has been introduced in 07/11/2013. The weakness was shared 09/02/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as ape demuxer: check for EOF in potentially long loops as confirmed git commit (GIT Repository). The advisory is shared at git.libav.org. The vendor cooperated in the coordination of the public release. The exploitability is told to be difficult. 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 53 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 (96939†). Further details are available at twitter.com. The entries VDB-10143, VDB-10144, VDB-10145 and VDB-10146 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- FFmpeg 2.0
- Libav 0.8.8/9.8
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/02/2013 🔍
09/02/2013 🔍
09/09/2013 🔍
08/21/2017 🔍
Sources
Product: ffmpeg.orgAdvisory: ape demuxer: check for EOF in potentially long loops
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10149
OSVDB: 96939
Misc.: 🔍
See also: 🔍
Entry
Created: 09/09/2013 14:14Updated: 08/21/2017 08:44
Changes: 09/09/2013 14:14 (53), 08/21/2017 08:44 (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.