FFmpeg 2.0 libavformat/utils.c estimate_timings_from_bit_rate integer coercion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in FFmpeg 2.0. Impacted is the function estimate_timings_from_bit_rate of the file libavformat/utils.c. This manipulation causes integer coercion.
No exploit exists.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability has been found in FFmpeg 2.0 (Multimedia Processing Software) and classified as very critical. Affected by this vulnerability is the function estimate_timings_from_bit_rate of the file libavformat/utils.c. The manipulation with an unknown input leads to a integer coercion vulnerability. The CWE definition for the vulnerability is CWE-192. Integer coercion refers to a set of flaws pertaining to the type casting, extension, or truncation of primitive data types. As an impact it is known to affect confidentiality, integrity, and availability.
The issue has been introduced in 07/11/2013. The weakness was disclosed 09/02/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as lavf: avoid integer overflow when estimating bitrate as confirmed git commit (GIT Repository). It is possible to read the advisory at git.libav.org. The public release has been coordinated in cooperation 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 of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around 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 53 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 (96937†). Additional details are provided at twitter.com. The entries VDB-10143, VDB-10144, VDB-10145 and VDB-10146 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: Integer coercionCWE: CWE-192 / CWE-189
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/02/2013 🔍
09/02/2013 🔍
09/09/2013 🔍
08/21/2017 🔍
Sources
Product: ffmpeg.orgAdvisory: lavf: avoid integer overflow when estimating bitrate
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10147
OSVDB: 96937
Misc.: 🔍
See also: 🔍
Entry
Created: 09/09/2013 14:14Updated: 08/21/2017 08:44
Changes: 09/09/2013 14:14 (52), 08/21/2017 08:44 (2)
Complete: 🔍
Cache ID: 216::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.