Yahoo! Assistant 3.6 - 'yNotifier.dll' ActiveX Control Memory Corruption Vulnerability

No description provided by source. source: http://www.securityfocus.com/bid/29065/info Yahoo! Assistant 'yNotifier.dll' ActiveX control is prone to a memory-corruption vulnerability. Successfully exploiting this issue may allow remote attackers to execute arbitrary code in the context of the...

CVE-2008-2111

The ActiveX Control yNotifier.dll in Yahoo! Assistant 3.6 and earlier allows remote attackers to execute arbitrary code via unspecified vectors in the Ynoifier COM object that trigger memory corruption...

Memory corruption

The ActiveX Control yNotifier.dll in Yahoo! Assistant 3.6 and earlier allows remote attackers to execute arbitrary code via unspecified vectors in the Ynoifier COM object that trigger memory corruption...

CVE-2008-2111

The ActiveX Control yNotifier.dll in Yahoo! Assistant 3.6 and earlier allows remote attackers to execute arbitrary code via unspecified vectors in the Ynoifier COM object that trigger memory corruption...

CVE-2008-2111

The CVE-2008-2111 entry concerns the ActiveX Control (yNotifier.dll) in Yahoo! Assistant 3.6 and earlier. The vulnerability is a memory corruption issue in the Ynoifier COM object that enables remote attackers to execute arbitrary code. Affected component: ActiveX/yNotifier.dll within Yahoo! Assi...

Yahoo! Assistant 3.6 - yNotifier.dll ActiveX Control Memory Corruption

Yahoo! Assistant 3.6 - yNotifier.dll ActiveX Control Memory Corruption source: https://www.securityfocus.com/bid/29065/info Yahoo! Assistant 'yNotifier.dll' ActiveX control is prone to a memory-corruption vulnerability. Successfully exploiting this issue may allow remote attackers to execute...

Yahoo! Assistant 3.6 - 'yNotifier.dll' ActiveX Control Memory Corruption

source: https://www.securityfocus.com/bid/29065/info Yahoo! Assistant 'yNotifier.dll' ActiveX control is prone to a memory-corruption vulnerability. Successfully exploiting this issue may allow remote attackers to execute arbitrary code in the context of the application using the affected ActiveX...