Nero ShowTime '.m3u' File Remote Buffer Overflow Vulnerability
BID:32446
Info
Nero ShowTime '.m3u' File Remote Buffer Overflow Vulnerability
| Bugtraq ID: | 32446 |
| Class: | Boundary Condition Error |
| CVE: |
CVE-2008-7079 |
| Remote: | Yes |
| Local: | No |
| Published: | Nov 24 2008 12:00AM |
| Updated: | Apr 16 2015 05:51PM |
| Credit: | Gjoko 'LiquidWorm' Krstic |
| Vulnerable: |
Nero ShowTime 5.0.15 0 |
| Not Vulnerable: | |
Discussion
Nero ShowTime '.m3u' File Remote Buffer Overflow Vulnerability
Nero ShowTime is prone to a remote buffer-overflow vulnerability because the application fails to perform adequate boundary checks on user-supplied input.
Attackers may leverage this issue to execute arbitrary code in the context of the application. Failed attacks will cause denial-of-service conditions.
NOTE: This issue may be related to BID 27615 (Nero Media Player M3U Buffer Overflow Vulnerability), but this has not been confirmed.
ShowTime 5.0.15.0 is vulnerable; other versions may also be affected.
Nero ShowTime is prone to a remote buffer-overflow vulnerability because the application fails to perform adequate boundary checks on user-supplied input.
Attackers may leverage this issue to execute arbitrary code in the context of the application. Failed attacks will cause denial-of-service conditions.
NOTE: This issue may be related to BID 27615 (Nero Media Player M3U Buffer Overflow Vulnerability), but this has not been confirmed.
ShowTime 5.0.15.0 is vulnerable; other versions may also be affected.
Exploit / POC
Nero ShowTime '.m3u' File Remote Buffer Overflow Vulnerability
The following proof-of-concept code is available:
The following proof-of-concept code is available:
Solution / Fix
Nero ShowTime '.m3u' File Remote 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].