FFmpeg 2.0 Sample Count libavformat/mov.c mov_read_stts Invalid Sample 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, has been found in FFmpeg 2.0. Affected is the function mov_read_stts of the file libavformat/mov.c of the component Sample Count Handler. Performing a manipulation as part of Invalid Sample results in an unknown weakness.
No exploit is available.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability, which was classified as problematic, was found in FFmpeg 2.0 (Multimedia Processing Software). This affects the function mov_read_stts of the file libavformat/mov.c of the component Sample Count Handler. The manipulation as part of a Invalid Sample leads to a unknown weakness. The impact remains unknown.
The issue has been introduced in 07/11/2013. The weakness was published 09/29/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as mov: Make sure the read sample count is nonnegative as confirmed git commit (GIT Repository). It is possible to read the advisory at git.libav.org. The public release has been coordinated with the project team. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 80 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 (97898†). Similar entries are available at VDB-10519, VDB-10518, VDB-10517 and VDB-10516. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- FFmpeg 2.0
- Libav 9.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: 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/29/2013 🔍
09/29/2013 🔍
10/01/2013 🔍
04/16/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: mov: Make sure the read sample count is nonnegative
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10515
OSVDB: 97898
See also: 🔍
Entry
Created: 10/01/2013 15:03Updated: 04/16/2019 07:48
Changes: 10/01/2013 15:03 (53), 04/16/2019 07:48 (1)
Complete: 🔍
Cache ID: 216:D5F:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.