FFmpeg 2.1 libavcodec/hnm4video.c decode_interframe_v4 memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in FFmpeg 2.1. This impacts the function decode_interframe_v4 of the file libavcodec/hnm4video.c. The manipulation results in memory corruption.
There is no exploit available.
A patch should be applied to remediate this issue.
Details
A vulnerability classified as very critical has been found in FFmpeg 2.1 (Multimedia Processing Software). Affected is the function decode_interframe_v4 of the file libavcodec/hnm4video.c. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.
The issue has been introduced in 10/29/2013. The weakness was shared 11/22/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as avcodec/hnm4video: check offset in decode_interframe_v4() more completely as confirmed git commit (GIT Repository). The advisory is available at git.videolan.org. The vendor cooperated in the coordination of the public release. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 04/17/2019).
The vulnerability was handled as a non-public zero-day exploit for at least 24 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 (100535†). The entries VDB-11398, VDB-11397, VDB-11396 and VDB-11395 are related to this item. If you want to get best quality of vulnerability data, you may have to visit 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: 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: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: git.videolan.org
Timeline
10/29/2013 🔍11/22/2013 🔍
11/22/2013 🔍
12/06/2013 🔍
04/17/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: avcodec/hnm4video: check offset in decode_interframe_v4() more completely
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-11394
OSVDB: 100535
See also: 🔍
Entry
Created: 12/06/2013 11:59Updated: 04/17/2019 11:09
Changes: 12/06/2013 11:59 (50), 04/17/2019 11:09 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.