FFmpeg 2.1 libavformat/4xm.c fourxm_read_packet Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in FFmpeg 2.1. The affected element is the function fourxm_read_packet of the file libavformat/4xm.c. This manipulation causes an unknown weakness.
No exploit exists.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability has been found in FFmpeg 2.1 (Multimedia Processing Software) and classified as problematic. Affected by this vulnerability is the function fourxm_read_packet of the file libavformat/4xm.c. The impact remains unknown.
The issue has been introduced in 10/29/2013. The weakness was disclosed 12/22/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as avformat/4xm: shrink packet if it was only partially initialized 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 exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 54 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.videolan.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 (101532†). The entries VDB-11681, VDB-11680, VDB-11679 and VDB-11678 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- FFmpeg 2.1
- Libav 0.8.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: 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.videolan.org
Timeline
10/29/2013 🔍12/22/2013 🔍
12/22/2013 🔍
12/31/2013 🔍
04/17/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: avformat/4xm: shrink packet if it was only partially initialized
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-11677
OSVDB: 101532
See also: 🔍
Entry
Created: 12/31/2013 12:31Updated: 04/17/2019 16:34
Changes: 12/31/2013 12:31 (51), 04/17/2019 16:34 (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.