FFmpeg 2.1 libavcodec/g2meet.c g2m_load_cursor memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FFmpeg 2.1. It has been classified as critical. Impacted is the function g2m_load_cursor of the file libavcodec/g2meet.c. This manipulation causes memory corruption.
There is not any exploit available.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in FFmpeg 2.1 (Multimedia Processing Software). It has been declared as critical. Affected by this vulnerability is the function g2m_load_cursor of the file libavcodec/g2meet.c. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability.
The issue has been introduced in 10/29/2013. The weakness was released 11/27/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as avcodec/g2meet: fix stride calculation, use correct format field as confirmed git commit (GIT Repository). The advisory is shared at git.videolan.org. The public release was coordinated with the project team. The exploitation appears to be difficult. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 29 days. During that time the estimated underground price was around $0-$5k.
Applying the patch Patchwork avcodec/g2meet: fix stride calculation/use correct format field is able to eliminate this problem. The bugfix is ready for download at patches.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 (100544†). Entries connected to this vulnerability are available at VDB-11404, VDB-11403, VDB-11402 and VDB-11400. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: 8.8VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.8
VulDB Temp Score: 8.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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: Patchwork avcodec/g2meet: fix stride calculation/use correct format field
Timeline
10/29/2013 🔍11/27/2013 🔍
11/27/2013 🔍
12/06/2013 🔍
04/17/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: avcodec/g2meet: fix stride calculation, use correct format field
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-11401
OSVDB: 100544
See also: 🔍
Entry
Created: 12/06/2013 14:21Updated: 04/17/2019 12:40
Changes: 12/06/2013 14:21 (52), 04/17/2019 12:40 (2)
Complete: 🔍
Committer:
Cache ID: 216::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.