FFmpeg 1.2 libavformat/mmsh.c mmsh_open_internal memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FFmpeg 1.2. It has been rated as problematic. This vulnerability affects the function mmsh_open_internal of the file libavformat/mmsh.c. The manipulation leads to memory corruption.
There is no exploit available.
Upgrading the affected component is advised.
Details
A vulnerability was found in FFmpeg 1.2 (Multimedia Processing Software) and classified as critical. This issue affects the function mmsh_open_internal of the file libavformat/mmsh.c. 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 issue has been introduced in 03/07/2013. The weakness was shared 06/07/2013 as mmsh: dont close context on seeking failure as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. The vendor cooperated in the coordination of the public release. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 92 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 0.11.4 eliminates this vulnerability. The upgrade is hosted for download at git.videolan.org. 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 3 months after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (97539†). The entries VDB-10413, VDB-10412, VDB-10411 and VDB-10410 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- FFmpeg 1.2
- Libav 0.8.7/9.7
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: 10.0VulDB Meta Temp Score: 9.5
VulDB Base Score: 10.0
VulDB Temp Score: 9.5
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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: FFmpeg 0.11.4
Patch: git.videolan.org
Timeline
03/07/2013 🔍06/07/2013 🔍
08/28/2013 🔍
09/23/2013 🔍
04/15/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: mmsh: dont close context on seeking failure
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10409
OSVDB: 97539
See also: 🔍
Entry
Created: 09/23/2013 14:44Updated: 04/15/2019 12:17
Changes: 09/23/2013 14:44 (52), 04/15/2019 12:17 (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.