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

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in VideoLAN VLC Media Player 2.0.1.0 and classified as problematic. This affects an unknown part of the component PMP File Handler. The manipulation leads to memory corruption. The attack can be initiated remotely. Additionally, an exploit exists. The presence of this vulnerability remains uncertain at this time.
Details
A vulnerability was found in VideoLAN VLC Media Player 2.0.1.0 (Multimedia Player Software) and classified as critical. This issue affects an unknown part of the component PMP File Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability.
The bug was discovered 03/15/2012. The weakness was released 03/15/2012 by Dan Fosco as vlc8.txt as not defined advisory (Website) via VLC v. 2.0.1.0 .pmp Memory Corruption. It is possible to read the advisory at dfcode.org. The vendor was not involved in 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 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. The exploit is available 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:
#include <stdio.h>
int main()
{
FILE *f;
int i;
f = fopen("dos.pmp", "w");
fputs("\x70\x6d\x70\x6d\x01", f);
for(i = 0; i < 9; i++)
{
fputc('\x00', f);
}
for(i = 0; i < 41; i++)
{
fputc('\x41', 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 (101469†). Entries connected to this vulnerability are available at VDB-11652 and VDB-11650. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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/15/2012 🔍03/15/2012 🔍
12/28/2013 🔍
05/06/2019 🔍
Sources
Vendor: videolan.orgAdvisory: vlc8.txt
Researcher: Dan Fosco
Status: Not defined
Disputed: 🔍
GCVE (VulDB): GCVE-100-11651
OSVDB: 101469
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 12/28/2013 14:49Updated: 05/06/2019 07:09
Changes: 12/28/2013 14:49 (54), 05/06/2019 07:09 (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.