DoctorDoom
02-17-2006, 07:14 AM
Description:
Two weaknesses have been reported in Winamp, which can be exploited by malicious people to cause a DoS (Denial of Service).
1) A boundary error during the handling of files with an .m3u file extension can be exploited to cause a buffer overflow via a specially crafted playlist containing a file with an overly long filename.
2) A boundary error during the handling of overly long filenames can be exploited to cause a buffer overflow via a playlist containing a file with an overly long filename.
Successful exploitation crashes the application. Arbitrary code execution may be possible, but has not been proven.
The weaknesses have been reported in version 5.13. Other versions may also be affected.
Solution:
Removing the mapping for .m3u and .pls extensions to Winamp.Winamp File Handling Buffer Overflow Weaknesses (http://secunia.com/advisories/18848/)
It's not a critical issue, and most likely can be ignored for now. This is just FYI.
Two weaknesses have been reported in Winamp, which can be exploited by malicious people to cause a DoS (Denial of Service).
1) A boundary error during the handling of files with an .m3u file extension can be exploited to cause a buffer overflow via a specially crafted playlist containing a file with an overly long filename.
2) A boundary error during the handling of overly long filenames can be exploited to cause a buffer overflow via a playlist containing a file with an overly long filename.
Successful exploitation crashes the application. Arbitrary code execution may be possible, but has not been proven.
The weaknesses have been reported in version 5.13. Other versions may also be affected.
Solution:
Removing the mapping for .m3u and .pls extensions to Winamp.Winamp File Handling Buffer Overflow Weaknesses (http://secunia.com/advisories/18848/)
It's not a critical issue, and most likely can be ignored for now. This is just FYI.