Posts Tagged ‘adobe-reader’

McAfee: IE Exploit to Blame for Chinese Google Hack

Friday, January 15th, 2010

Security firm McAfee said today that the recent China-based attack on Google and other companies was the result of a new security hole in Internet Explorer . McAfee says the vulnerability is not publicly known, but they have informed Microsoft and expects them to take action soon. So a Microsoft product could be the indirect cause of Google pulling out of China. This must be Microsoft’s favorite software vulnerability ever.

For the full story, go to Maximum PC

Adobe: Hang Tight, We’ll Fix Things Next Month

Thursday, December 17th, 2009

The other day, Adobe announced it had discovered a vulnerability in its Adobe Reader and Acrobat 9.2 and earlier versions being exploited in the wild, and assured users the company was investigating the issue. The good news is that Adobe’s security team has finished the investigation. And the bad news? You’ll have to wait until at least January 12, 2010 — the targeted ship date — to receive a patch

For the full story, go to Maximum PC

[MINI HOW-TO] How To Disable Javascript in Adobe Reader and Patch the Latest Massive Security Hole

Tuesday, December 15th, 2009

Once again, Adobe has confirmed a gigantic security hole in their buggy, bloated, and completely insecure Adobe PDF Reader application. This isn’t the first time, either—it’s like a non-stop barrage of security holes from Adobe products. There’s also no antivirus application checking for this security hole, so don’t think you’re safe yet… the latest hole requires disabling Javascript in Adobe Reader, and to do that, you’ll need to head into Edit –> Preferences, and then find the JavaScript category on the left-hand side. Once you are there, you can disable JavaScript by simply unchecking the “Enable Acrobat JavaScript” box

The full story can be found on How To Geek

Mozilla Admits that Firefox has CPU Usage Problems

Monday, November 23rd, 2009

Is your ultraportable overheating while surfing the web? As odd as it sounds, the culprit could be Firefox rather than a hardware issue. No, really, check out what one of Mozilla’s support pages has to say on the matter.

For the full story, go to Maximum PC