FFmpeg 2.0 Max Samples Per Frame libavcodec/alac.c alac_set_info 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 2.0 and classified as critical. Affected by this issue is the function alac_set_info of the file libavcodec/alac.c of the component Max Samples Per Frame Handler. Such manipulation leads to memory corruption.
There is no exploit available.
A patch should be applied to remediate this issue.
Details
A vulnerability, which was classified as very critical, has been found in FFmpeg 2.0 (Multimedia Processing Software). Affected by this issue is the function alac_set_info of the file libavcodec/alac.c of the component Max Samples Per Frame Handler. 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 07/11/2013. The weakness was shared 09/03/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as alac: Limit max_samples_per_frame as confirmed git commit (GIT Repository). The advisory is available at git.libav.org. The vendor cooperated in the coordination of the public release. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. 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 08/21/2017).
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.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 (96949†). twitter.com is providing further details. The entries VDB-10143, VDB-10144, VDB-10145 and VDB-10146 are related to this item. If you want to get best quality of vulnerability data, you may have to visit 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: 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.libav.org
Timeline
07/11/2013 🔍09/03/2013 🔍
09/03/2013 🔍
09/09/2013 🔍
08/21/2017 🔍
Sources
Product: ffmpeg.orgAdvisory: alac: Limit max_samples_per_frame
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10154
OSVDB: 96949
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 (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.