Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

But the vast majority are memory corruption and sandbox escape issues.

...which require JS to exploit. (What is a "sandbox escape" if there isn't code to... escape it?)

I went through the 50 vulnerabilities on that page and looked at the nature of them and inspected any PoC code if any. This is the results:

PDF,JS,JS,WebGL(JS),JS,CSS,JS,JS,extension,HTML(but PoC needs JS),JS,PDF,PDF,MIDI(JS),AppCache(JS),PDF,JS,UI,WebRTC(JS),JS,JS(speech recognition!?),JS,JS,JS,JS,JS,JS,JPEG(rendering uninitialised memory --- not exploitable without JS to read that data),JS(WebWorker),HTTP/SSL(!),SVG+JS,UI,JS,XML(!),SVG+JS,JS(audio),Fonts(actually Windows font renderer bug),UI,??(no details available),IndexedDB(JS),WebGL(JS),UI,JS(WebSockets),NaCl(extension),extension,PNG,WebGL(JS),?,JS,WebGL(JS)

That's 32/50 confirmed to require JS to exploit, and only 3/50 stood out as being "visit a page with all plugins/JS/extensions disabled, and still get pwned", of which 1 is actually a Windows bug.

Disabling JavaScript insulates you from a nontrivial - but nontheless minority - subset of browser vulnerabilities.

Looks more like a majority to me.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: