FFmpeg 1.2.2/2.0 libavcodec/aasc.c aasc_decode_frame Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in FFmpeg 1.2.2/2.0. This impacts the function aasc_decode_frame of the file libavcodec/aasc.c. This manipulation causes an unknown weakness.
No exploit is available.
It is suggested to install a patch to address this issue.
Details
A vulnerability classified as problematic was found in FFmpeg 1.2.2/2.0 (Multimedia Processing Software). Affected by this vulnerability is the function aasc_decode_frame of the file libavcodec/aasc.c. As an impact it is known to affect confidentiality.
The issue has been introduced in 07/28/2013. The weakness was published 07/28/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as aasc: Check minimum buffer size as confirmed git commit (GIT Repository). The advisory is shared at git.libav.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 are known, but no exploit is available.
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 (95977†). Similar entries are available at VDB-9868, VDB-9866, VDB-9864 and VDB-9863. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- FFmpeg 1.2.2/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/28/2013 🔍07/28/2013 🔍
07/28/2013 🔍
08/09/2013 🔍
04/15/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: aasc: Check minimum buffer size
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9865
OSVDB: 95977
See also: 🔍
Entry
Created: 08/09/2013 10:39Updated: 04/15/2019 16:56
Changes: 08/09/2013 10:39 (50), 04/15/2019 16:56 (1)
Complete: 🔍
Cache ID: 216:4C2: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.