FFmpeg 2.0 Channel Decoding Offset libavcodec/alac.c alac_decode_frame 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, was found in FFmpeg 2.0. Affected is the function alac_decode_frame of the file libavcodec/alac.c of the component Channel Decoding Offset Handler. The manipulation results in an unknown weakness.
No exploit exists.
Applying a patch is advised to resolve this issue.
Details
A vulnerability classified as problematic has been found in FFmpeg 2.0 (Multimedia Processing Software). Affected is the function alac_decode_frame of the file libavcodec/alac.c of the component Channel Decoding Offset Handler. The impact remains unknown.
The issue has been introduced in 07/11/2013. The weakness was disclosed 09/03/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as alac: Check that the channels fit at the given offset as confirmed git commit (GIT Repository). The advisory is shared for download at git.libav.org. The public release has been coordinated in cooperation with the vendor. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, 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.libav.org. A possible mitigation has been published immediately after the disclosure of the vulnerability. The git commit contains the following remark:
The code tries to decode a number of channels at the offset given by the ff_alac_channel_layout_offsets table. Even if the number of channels decoded so far doesn't exceed the total number of channels, we need to check that we actually can decode that number of channels at this offset as well.
The vulnerability is also documented in the vulnerability database at OSVDB (96944†). Further details are available at twitter.com. The entries VDB-10143, VDB-10144, VDB-10145 and VDB-10146 are pretty similar. VulDB is the best source for vulnerability data and more expert information about this specific topic.
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: 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.libav.org
Timeline
07/11/2013 🔍09/03/2013 🔍
09/03/2013 🔍
09/09/2013 🔍
08/21/2017 🔍
Sources
Product: ffmpeg.orgAdvisory: alac: Check that the channels fit at the given offset
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10152
OSVDB: 96944
Misc.: 🔍
See also: 🔍
Entry
Created: 09/09/2013 14:14Updated: 08/21/2017 08:44
Changes: 09/09/2013 14:14 (54), 08/21/2017 08:44 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.