Описание
Stack-based buffer overflow in gen_jumpex.dll in Winamp before 5.64 Build 3418 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a package with a long Skin directory name. NOTE: a second buffer overflow involving a long GUI Search field to ml_local.dll was also reported. However, since it is only exploitable by the user of the application, this issue would not cross privilege boundaries unless Winamp is running under a highly restricted environment such as a kiosk.
Stack-based buffer overflow in gen_jumpex.dll in Winamp before 5.64 Build 3418 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a package with a long Skin directory name. NOTE: a second buffer overflow involving a long GUI Search field to ml_local.dll was also reported. However, since it is only exploitable by the user of the application, this issue would not cross privilege boundaries unless Winamp is running under a highly restricted environment such as a kiosk.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2013-4694
- https://exchange.xforce.ibmcloud.com/vulnerabilities/85399
- https://www.rcesecurity.com/2013/07/winamp-v5-64-fixes-several-code-execution-vulnerabilities-cve-2013-4694-cve-2013-4695
- http://forums.winamp.com/showthread.php?t=364291
- http://osvdb.org/94739
- http://osvdb.org/94740
- http://packetstormsecurity.com/files/122239/WinAmp-5.63-Buffer-Overflow.html
- http://packetstormsecurity.com/files/122978
- http://seclists.org/fulldisclosure/2013/Jul/4
- http://www.exploit-db.com/exploits/26558
- http://www.securityfocus.com/bid/60883
- http://www.securitytracker.com/id/1030107
Связанные уязвимости
Stack-based buffer overflow in gen_jumpex.dll in Winamp before 5.64 Build 3418 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a package with a long Skin directory name. NOTE: a second buffer overflow involving a long GUI Search field to ml_local.dll was also reported. However, since it is only exploitable by the user of the application, this issue would not cross privilege boundaries unless Winamp is running under a highly restricted environment such as a kiosk.