The Hindu News Update - Associated PressAP wrote:San Francisco, Jan. 4 (AP): Computer security researchers said they have discovered a vulnerability in Adobe Systems Inc.'s ubiquitous Acrobat Reader software that allows cyber-intruders to attack personal computers through trusted Web links.
Virtually any Web site hosting Portable Document Format, or PDF, files are vulnerable to attack, according to researchers from Symantec Corp. and VeriSign Inc.'s iDefense Intelligence.
The attacks could range from stealing cookies that track a user's Web browsing history to the creation of harmful worms, the researchers said Wednesday.
------
The flaw appears to target Microsoft Corp.'s Internet Explorer 6.0 Web browser and earlier versions, and Mozilla's Firefox browser, the researchers said.
They recommended that users protect themselves by upgrading Internet Explorer or changing Firefox's user options so the browser does not use the Acrobat plug-in.
M-Dollar - Ars Technica JournalArs Technica Journals wrote:This morning, Symantec's Hon Lau warned of the attack on the Symantec Security Response Weblog. He cautioned that even trusted websites could fall victim to this problem.
Any Web site that hosts a .pdf file can be used to conduct this attack. All the attacker has to do is find out who is hosting a .pdf file on their Web server and then piggy back on it to mount an attack. What this means, in a nutshell, is that anybody hosting a .pdf file, including well-trusted brands and names on the Web, could have their trust abused and become unwilling partners in crime.
Personally, I was able to validate the proof of concept code with Adobe Reader versions 6 and 7; however, Adobe Reader 8 prevented the code execution and presented me with an "Operation Not Allowed" dialog box. The validation was done in both Opera 9.10 and Firefox 2.0.0.1. Internet Explorer's Adobe Reader ActiveX plugin is not susceptible to this problem.
Obviously, one way to protect your PC from this vulnerability is to upgrade to Adobe Reader 8. If you'd prefer not to upgrade, Hon Lau also has a workaround posted on the Symantec Security Response Weblog.





