If you are a Chrome for Mac OS user, chances are that you’re working your way through a seemingly never-ending battle with an onslaught of Adobe (Shockwave) Flash updates, many of which have seemed to cause unnecessary slow-downs, crashes and eventually (pardon my highly scientific terminology) the urge to rip out each and every single hair from your skull.

'We are reviewing our security update process in order to mitigate risks in Shockwave Player,' Edell said.After much popularity of my original post last year on how to fix Shockwave Flash crashing within Chrome for Mac, I’m back with an updated version for 2013! Because of this, it may be easier to exploit a vulnerability when Flash is hosted by Shockwave, for example.'Īdobe spokeswoman Heather Edell confirmed that CERT's information is correct, and that the next release of Shockwave Player will include the updated version of Flash Player. In the case of Shockwave, there are some mitigations missing in a number of modules, such as SafeSEH. 'One of the things that helps make a vulnerability more difficult is how many of the exploit mitigations a vendor opts in to. 'So not only are the vulnerabilities there, but they're easier to exploit as well,' Dormann said. That's because Shockwave has several modules that don't opt in to trivial exploit mitigation techniques built into Microsoft Windows, such as SafeSEH. Dormann said he initially alerted the public to this gaping security hole in 2012 via this advisory, but that he first told Adobe about this lacklustre update process back in 2010.Īs if that weren't bad enough, Dormann said it may actually be easier for attackers to exploit Flash vulnerabilities via Shockwave than it is to exploit them directly against the stand-alone Flash plug-in itself.

Adobe shockwave not working chrome