PatPlayer '.m3u' File Heap Buffer Overflow Vulnerability
BID:43750
Info
PatPlayer '.m3u' File Heap Buffer Overflow Vulnerability
| Bugtraq ID: | 43750 |
| Class: | Boundary Condition Error |
| CVE: |
CVE-2009-3717 |
| Remote: | Yes |
| Local: | No |
| Published: | Jul 10 2009 12:00AM |
| Updated: | Jul 10 2009 12:00AM |
| Credit: | Cyber-Zone |
| Vulnerable: |
LucVil PatPlayer 3.9 |
| Not Vulnerable: | |
Discussion
PatPlayer '.m3u' File Heap Buffer Overflow Vulnerability
PatPlayer is prone to a heap-based buffer-overflow vulnerability because the application fails to bounds-check user-supplied data before copying it into an insufficiently sized buffer.
Attackers can execute arbitrary code in the context of the affected application. Failed exploit attempts will result in a denial-of-service condition.
PatPlayer 3.9 is vulnerable; other versions may also be affected.
PatPlayer is prone to a heap-based buffer-overflow vulnerability because the application fails to bounds-check user-supplied data before copying it into an insufficiently sized buffer.
Attackers can execute arbitrary code in the context of the affected application. Failed exploit attempts will result in a denial-of-service condition.
PatPlayer 3.9 is vulnerable; other versions may also be affected.
Exploit / POC
PatPlayer '.m3u' File Heap Buffer Overflow Vulnerability
An attacker can exploit this issue by enticing an unsuspecting victim to open a playlist file using the affected application.
The following proof-of-concept code is available:
An attacker can exploit this issue by enticing an unsuspecting victim to open a playlist file using the affected application.
The following proof-of-concept code is available:
Solution / Fix
PatPlayer '.m3u' File Heap Buffer Overflow Vulnerability
Solution:
Currently we are not aware of any vendor-supplied patches. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].
Solution:
Currently we are not aware of any vendor-supplied patches. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].