| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in FFmpeg. Affected by this issue is the function g2m_decode_frame of the file libavcodec/g2meet.c. This manipulation of the argument Cursor causes array index.
There is no exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as critical was found in FFmpeg (Multimedia Processing Software) (affected version not known). Affected by this vulnerability is the function g2m_decode_frame of the file libavcodec/g2meet.c. The manipulation of the argument Cursor with an unknown input leads to a array index vulnerability. The CWE definition for the vulnerability is CWE-129. The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was shared 06/09/2013 by Mateusz Jurczyk and Gynvael Coldwind as g2meet: Check cursor parameters before writing them in the context 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 appears to be difficult. The attack can only be initiated within the local network. 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.videolan.org. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at OSVDB (94132†) and Secunia (SA53766†). The entries VDB-9107, VDB-9108, VDB-9129 and VDB-9130 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
- Libav
Product
Type
Name
License
Website
- Product: https://ffmpeg.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.6VulDB Meta Temp Score: 9.2
VulDB Base Score: 9.6
VulDB Temp Score: 9.2
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: Array indexCWE: CWE-129 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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.videolan.org
Timeline
06/09/2013 🔍06/09/2013 🔍
06/12/2013 🔍
06/19/2013 🔍
08/26/2017 🔍
Sources
Product: ffmpeg.orgAdvisory: g2meet: Check cursor parameters before writing them in the context
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9109
Secunia: 53766 - FFmpeg Multiple Vulnerabilities, Moderately Critical
OSVDB: 94132
See also: 🔍
Entry
Created: 06/12/2013 12:50Updated: 08/26/2017 06:41
Changes: 06/12/2013 12:50 (52), 08/26/2017 06:41 (1)
Complete: 🔍
Committer:
Cache ID: 216::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.