4 ms·
Seems a bit pre-emptive, as the suggestion is based on "a critical yet unknown vulnerability" that was "probably exploited" in the recent attack on Google & oth
by Groxx 17y ago
Seems a bit pre-emptive, as the suggestion is based on "a critical yet unknown vulnerability" that was "probably exploited" in the recent attack on Google & others.
That said, the very fact that a browser is not super-sandboxed in the first place is frightening, and IE has a huge amount of integration compared to other browsers. Mayhaps that's why it's been such a problem?
- tptacek 17y agoIt was probably preemptive when it was written, but it's been borne out by the facts. The only browser that is "super sandboxed" is Chrome, and nobody knows how effective the process security model in Chrome is going to end up being. The actual vulnerability appears to be a basic object lifespan problem in DOM handling code; in other words, this could happen to any browser. After Chrome, the browser with the next most involved security model is IE with DEP, and, in fact, when DEP is enabled, the exploit doesn't work (that's no guarantee that it could never work, though).