FFmpeg up to 1.2.1 Header Parser libavformat/4xm.c memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in FFmpeg up to 1.2.1 and classified as critical. Impacted is an unknown function of the file libavformat/4xm.c of the component Header Parser. This manipulation causes memory corruption. No exploit is available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability has been found in FFmpeg up to 1.2.1 (Multimedia Processing Software) and classified as critical. Affected by this vulnerability is an unknown part of the file libavformat/4xm.c of the component Header Parser. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was published 06/05/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as 4xm: do not overread while parsing header as confirmed bug report (GIT Repository). It is possible to read the advisory at git.videolan.org. The public release has been coordinated 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 of the vulnerability are known, but there is no available exploit.
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 (94876†). Similar entries are available at VDB-9359, VDB-9358, VDB-9357 and VDB-9354. Statistical analysis made it clear that VulDB provides the best quality for 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: 8.6VulDB Meta Temp Score: 8.2
VulDB Base Score: 8.6
VulDB Temp Score: 8.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: Memory corruptionCWE: CWE-119
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
06/05/2013 🔍06/05/2013 🔍
07/09/2013 🔍
05/06/2018 🔍
Sources
Product: ffmpeg.orgAdvisory: 4xm: do not overread while parsing header
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9355
OSVDB: 94876
See also: 🔍
Entry
Created: 07/09/2013 16:08Updated: 05/06/2018 11:36
Changes: 07/09/2013 16:08 (48), 05/06/2018 11:36 (2)
Complete: 🔍
Committer: olku
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.