20
Sep 10

Security Fix for Critical Adobe Flash Flaw

facebooktwittergoogle_plusredditpinterestlinkedinmail

Adobe Systems Inc. today rushed out a software update to remedy a dangerous security hole in its ubiquitous Flash Player that hackers have been exploiting to break into vulnerable systems.

Adobe recommends users of Adobe Flash Player 10.1.82.76 and earlier versions for Windows, Macintosh, Linux, and Solaris update to Adobe Flash Player 10.1.85.3, and users of Adobe Flash Player 10.1.92.10 for Android update to Adobe Flash Player 10.1.95.1. Updates are available from this link.

Adobe’s advisory on this flaw is here. The same security vulnerability also exists in the latest versions of Adobe Reader and Acrobat, although Adobe says it doesn’t plan to fix this vulnerability in those products until the week of Oct. 4.

Note that if you use both Internet Explorer and non-IE browsers, you’re going to need to apply this update at least twice, once by visiting the Flash Player installation page with IE and then again with Firefox, Opera or Safari. Google Chrome users can update to Chrome 6.0.472.62 to grab this latest Flash update. To check which version of Flash you have installed, visit this link.

Also, unless you want some “free” software — like McAfee Security Scan or whatever browser toolbar Adobe is bundling with Flash player this month — remember to uncheck that option before you agree to download the software.

Tags: , ,

24 comments

  1. Call me cynical, but could it be Adobe actually desires numerous vulnerabilities in their products? Each patched installation is another opportunity for them to get paid for toolbar installation. Most people uncheck the box, but if you have to do it EVERY SINGLE G-D D-MN MONTH you’ll probably forget at some point and WHAM-O that’s a nickel in Adobe’s piggy bank.

    What a piece of junk. HTML5 can’t get here soon enough; even if it has problems it couldn’t be this bad. Hell even Silverlight could be a better alternative.

  2. What’s this crapware “New York Times Reader” they snuck in with their Firefox update?

    They didn’t even ask.

    • My install, using the unfortunate Adobe Download Mangler, had a banner ad for TimesReader 2.0 and an “Add to Download” button you had to push. I wonder if they changed the installer from opt-out to opt-in between your post and mine?

      • For my luck, I use Ubuntu (Linux) for everything else, and Windows Only For Gaming, thus I lack problems like ADM, because flash-plugin gets updated as like all other regular updates on Ubu.

        Just remember to slam your head on the wall if you forget to shut Firefox while running the updating, because you most likely need to reinstall flash-plugin – if you ever notice that updating did fail.

  3. Although it’s been mentioned in previous Adobe Flash posts’ comments threads, it’s worth repeating that to sidestep the irksome Adobe Download Manager (Adobe DLM), one can download manual installers for both IE and non-IE browsers at

    http://kb2.adobe.com/cps/191/tn_19166.html#main_ManualInstaller

  4. WOW! Thanks Brian!

    Who needs Secunia or File Hippo when we have BK watching our back!!! :)

  5. Bypass all the “tag-alongs”:

    ___

    Direct download current version – executable Flash Player installer…
    http://fpdownload.adobe.com/get/flashplayer/current/install_flash_player_ax.exe
    For IE …
    http://fpdownload.adobe.com/get/flashplayer/current/install_flash_player.exe
    For Firefox, other browsers, etc…

    Flash test site: http://www.adobe.com/software/flash/about/
    … should read: “You have version 10,1,85,3 installed”
    .

    • Excellent advice! One more step many may find useful is the uninstaller:

      http://kb2.adobe.com/cps/141/tn_14157.html

      I’ve always used the uninstaller first, then installed the new version (using the exe installer you reference above). Works like a charm everytime.

      Note: to minimize having to reboot, be sure to close all open programs that may be using Flash (ex. browsers, IM clients, see step 3 in the uninstaller link above). :)

  6. When installing the Flash plug-in for Firefox remember to allow scripts on adobe.com if you use NoScript.

    I also had to disable Microsoft Security Essentials real time protection before the FF plug-in would install on my laptop. I’m not sure why, since the Flash plug-in had already installed on IE8 without my having to do that.

    • The Adobe page does warn that one may have to turn off any AV or AS solution to install the update. Since I don’t like doing that, I simply rebooted.

  7. As usual, Adobe’s web site falsely claims that my IE8-32 is IE8-64, so it won’t allow me to get the latest update.

    Adobe’s web site would, however, be willing to install Flash-64 Beta on IE8-32. How helpful – NOT.

    (My previous workaround on this issue no longer works.)

  8. Of course, if you’d had the Chrome browser, you’d have already been updated about 48 hours ago with it’s built in Flash plugin! ;-)

    Cheers!

  9. Thank you, Brian. Your “time to patch” reminders are always helpful and are appreciated by your less computer-savvy readers!

  10. Perhaps Adobe is not overly concerned with vending a secure product . After all, they can only push the useless toolbar and plug-ins via new installs and updates.

  11. thanks, alex for reminding us that we can bypass adobe DLM by doing a manual install. i did that with no problem.

  12. XP, SP3. Using the Adobe DLM in Firefox, the error: “Adobe Flash Player 10.1″ “The download did not pass the integrity check (16291.304.428)”. Clicked OK.

    The DLM says there was an error and it did not install correctly, but then Adobe’s “success” page opened and said it had correctly installed Version 10.1.82.76 — not the latest 85.3 version. Despite the DLM error dialog, I can imagine lots of folks could be easily misled into thinking Flash had indeed updated correctly because the “success” page opens.

  13. If you haven’t done so already, be sure to configure your Adobe Flash Global Storage Settings panel to (attempt) to turn off Flash cookies and tracking capabilities. And Firefox users should install/configure both the TACO and BetterPrivacy plugins to kill Flash tracking cookies.

    It’s a scandal that the default Flash setting invade everyone’s privacy, and that controlling them requires visiting this obscure website.

    I hope that the recent lawsuits (see NYT, Code That Tracks Users’ Browsing Prompts Lawsuits) are costly enough to stop this odious industry practice.

  14. Is there ANY progress on getting Adobe to build an auto-updater?

    You wrote about this as far back as 2006, and seemed to get the attention of some Adobe product manager at the time. But their promises never materialized and now we’re faced with, as you say, a sad patch history that rivals Microsoft. The difference, of course, is that Microsoft has an effective auto-updater, while Abode has a defective, sometimes-it-works-sometimes-is-doesn’t update process that’s painfully manual.

    The cynics who suggest this is deliberate on Adobe’s part–just to get clickthroughs for their flavor-of-the-month add-ins–is starting to ring true.

    While the technically adept can work their way through this minefield, our less-sophisticated users have no chance.

    Here’s the business model for making zillions: build a service that will keep this bleeping computer patched!

    • 9.2 and 8.3 of Acrobat now have an auto-update auto-install option under preferences.

      Flash has a similiar thing, but it runs when windows boots and warns you at boot time. Doesn’t seem to work all the time and there’s no GUI or anything. It either works or it doesn’t.

      Adobe needs to default to make all this stuff auto-update via a dedicated app like the Apple Update manager, instead of multiple mechanisms.

      • > 9.2 and 8.3 of Acrobat now have an auto-update auto-install option under preferences.

        They do. But it’s not reliable, and it’s almost never timely. I think it was in another Krebs post that I saw Adobe admit that they don’t trigger the auto-update right away when a patch is available–it would cause too much of a strain on their servers, and they want to “make sure” the patch is working properly.

        In a day zero patch situation, that’s simply Not Acceptable.

        Adobe even messes up the manual patch process–in a day zero situation Adobe rolls out the patched version on one update page, but still leaves the old version hanging around on other update pages. So your success depends on 1) guessing which page is up to date, 2) avoiding the wrong page and 3) double-checking that the patch actually got applied.

        Show of hands: how many people “update their flash by uninstalling and re-installing?

        Yeesh.

        on depending on which Web page you go toEven patching manually invokeAdobe seems to


Read previous post:
Google Adds 2-Factor Security to Gmail, Apps

Google said today that it will begin offering users greater security protections for signing in to Gmail and other Google...

Close