VideoLAN VLC Media Player 2.0.1.0 TTA File memory corruption ⚔ [Disputed]

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in VideoLAN VLC Media Player 2.0.1.0. Affected by this issue is some unknown functionality of the component TTA File Handler. Executing a manipulation can lead to memory corruption. It is possible to launch the attack remotely. Furthermore, an exploit is available. The existence of this vulnerability is still disputed at present.
Details
A vulnerability has been found in VideoLAN VLC Media Player 2.0.1.0 (Multimedia Player Software) and classified as critical. This vulnerability affects some unknown functionality of the component TTA File Handler. 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 bug was discovered 03/18/2012. The weakness was published 03/18/2012 by Dan Fosco as vlc10.txt as not defined exploit (Website). The advisory is available at dfcode.org. The vendor was not involved in the coordination of the public release. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are unknown but a public exploit is available. OSVDB notes: "Based on the provided details and additional cursory testing, there is, however, no evidence to support the claims of memory corruption and the possibility of code execution. Instead, the issue is simply considered a stability bug, causing this entry to be flagged as 'Myth/Fake'."
A public exploit has been developed by Dan Fosco in ANSI C. It is possible to download the exploit at dfcode.org. It is declared as proof-of-concept. The real existence of this vulnerability is still doubted at the moment. The code used by the exploit is:
int main(int argc, char *argv[])
{
FILE *f;
f = fopen(argv[1], "r+");
fseek(f, 10, SEEK_SET);
fputc('\x00', f);
fseek(f, 11, SEEK_SET);
fputc('\x00', f);
fseek(f, 26, SEEK_SET);
fputc('\x00', f);
fseek(f, 68, SEEK_SET);
fputc('\x00', f);
fseek(f, 59, SEEK_SET);
fputc('\x00', f);
fclose(f);
return 0;
}There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at OSVDB (101468†). Similar entries are available at VDB-11652 and VDB-11651. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.videolan.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.1
VulDB Base Score: 10.0
VulDB Temp Score: 9.1
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: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Dan Fosco
Programming Language: 🔍
Download: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/18/2012 🔍03/18/2012 🔍
12/28/2013 🔍
05/06/2019 🔍
Sources
Vendor: videolan.orgAdvisory: vlc10.txt
Researcher: Dan Fosco
Status: Not defined
Disputed: 🔍
GCVE (VulDB): GCVE-100-11650
OSVDB: 101468
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 12/28/2013 14:46Updated: 05/06/2019 07:09
Changes: 12/28/2013 14:46 (53), 05/06/2019 07:09 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.