A remote illegal access vulnerability exists in Microsoft Windows Live Messenger. A vicious attacker can control the Live Messenger via constructing a malicious web page, once the victim visits this page, the attacker can control the local Live Messenger, including disclosing personal sensitive information of Live Messenger, transferring local audio and video information to remote and so on.
Affected Software Versions:
Microsoft Windows Live Messenger 4.7 on Windows XP and Windows Server 2003 Microsoft Windows Live Messenger 5.1 on Windows 2000, Windows XP and Windows Server 2003
Details:
When installing Windows XP, an old edition of MSN Messenger is installed automatically. The old edition opens the MSN API to develop as an ActiveX Control, and marks it with "safe".
By using this ActiveX Control, we can control the local MSN Messenger, for instance: change state, gain current login ID, steal contact-person's information, send mail using the victim's name, and so on, all of these functions given by this feature can be considered to be security problems.
Even the user installs a higher edition of MSN Messenger(Windows Live Messenger), this ActiveX control will not be removed. By using this we will still be allowed to visit the local Live Messenger.
Solution:
Microsoft has released an advisory for this vulnerability which can be found at:
An illegal resource reference vulnerability exists in the ActiveX Control of RealNetworks RealPlayer. For exploiting the vulnerability, the attacker may build a special web page and entrap the victim into visiting it, if the local system has installed RealPlayer, the local resources (or any other illegal resources) will be accessed. This vulnerability may assist in exploitation of other vulnerabilities.
Affected Software Versions:
RealPlayer 10.6 and previous versions (other versions may also be affected)
Details:
Currently there is no details released.
Solution:
The vendor has fixed this vulnerability, the vendor's advisory is available on:
2006.12.19 Vendor notified 2006.12.20 Vendor responded 2008.07.23 Notified by the vendor that patch and advisory were coming 2008.07.25 Vendor's advisory released 2008.07.29 Advisory released