I’m always amused by the “turn off javascript” guidance when almost all of the exploits don’t need it. Sure there a few nasty privacy violation things that can only be done with it on, but telling people to turn off JS is like telling them to only run “Trusted” software… whatever that means.
Note that Adobe has been using CVE identifiers in their advisories since 2005.
In this case, Adobe asked for a CVE identifier aproximately 24 hours before they published. Since a zero-day exploit prompted the advisory, they likely thought it was better to publish than to wait for a response from me.
CVE is not set up well for rapid response, although we are working on it, and I try to handle reservation requests quickly.
Thank you Steve for pointing out the circumstances and Adobe’s track record. It would make sense to cut a few corners to issue an urgently needed advisory.
Thanks for all the work that you do.
Enabling Javascripts can cause vital privacy Violations. But as you said without it many things aren’t possible too!
Andy,
Most of the *browser* exploits need JavaScript. Turning off JavaScript does make browsing the web much safer. As time goes on, it becomes more difficult to do so as more functionality is lost. However, a lot of that functionality is also not for your benefit. JavaScript is a huge headache because it makes the browser lack transparency, purity, obedience and loyalty (c.f. “Software Properties and Behaviors”, http://homes.cerias.purdue.edu/~pmeunier/aboutme/poster52D-07F(Meunier).pdf)
on Friday, February 20, 2009 at 02:35 PM