FFmpeg 2.1 libavformat/mov.c mov_read_udta_string uninitialized resource
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in FFmpeg 2.1 and classified as problematic. The affected element is the function mov_read_udta_string of the file libavformat/mov.c. The manipulation leads to uninitialized resource.
It is possible to initiate the attack remotely. There is no exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in FFmpeg 2.1 (Multimedia Processing Software) and classified as critical. This issue affects the function mov_read_udta_string of the file libavformat/mov.c. The manipulation with an unknown input leads to a uninitialized resource vulnerability. Using CWE to declare the problem leads to CWE-908. The product uses or accesses a resource that has not been initialized. The impact remains unknown.
The issue has been introduced in 10/29/2013. The weakness was shared 01/14/2014 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as avcodec/flashsv: check avio_read() return in mov_read_udta_string() as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. The vendor cooperated in the coordination of the public release. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 77 days. During that time the estimated underground price was around $0-$5k.
Applying the patch avcodec/flashsv: check avio_read() return in mov_read_udta_string() is able to eliminate this problem. The bugfix is ready for download at git.videolan.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 (102330†). The entries VDB-12030, VDB-12028, VDB-12027 and VDB-12026 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- FFmpeg 2.1
- Libav 0.8.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: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: Uninitialized resourceCWE: CWE-908
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: avcodec/flashsv: check avio_read() return in mov_read_udta_string()
Timeline
10/29/2013 🔍01/14/2014 🔍
01/14/2014 🔍
01/22/2014 🔍
12/17/2018 🔍
Sources
Product: ffmpeg.orgAdvisory: avcodec/flashsv: check avio_read() return in mov_read_udta_string()
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-12029
OSVDB: 102330
See also: 🔍
Entry
Created: 01/22/2014 13:33Updated: 12/17/2018 07:55
Changes: 01/22/2014 13:33 (52), 12/17/2018 07:55 (2)
Complete: 🔍
Cache ID: 216:3F6:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.