3 ms·
Do you have a source? I tried googling javascript runtime (primarily v8) exploitation and haven't been able to find any examples of this ever happening. Edit:
by dmix 14y ago
Do you have a source?
I tried googling javascript runtime (primarily v8) exploitation and haven't been able to find any examples of this ever happening.
Edit: I'm not saying its not plausible, but wouldn't it require root/user access? What benefit would it provide over other type of attacks with that level of access? Just because there's no browser tools to check for it?
- marshray 14y agoThis looks like a good read: http://www.adambarth.com/papers/2009/barth-weinberger-song.pdf http://www.adambarth.com/papers/2009/barth-weinberger-song.p... Cross-Origin JavaScript Capability Leaks: Detection, Exploitation, and Defense Although these vulnerabilities are imple- mentation errors in WebKit, the presence of the bugs illustrates the fragility of the general architec- ture. (Other browsers have historically had similar vulnerabilities [17, 18, 19].) We detail these vulner- abilities and construct proof-of-concept exploits to demonstrate how an attacker can leverage a leaked JavaScript pointer to inject a malicious script into an honest security origin.
- dmix 14y agoThanks I'll check it out, but I thought that tptacek was talking about manipulation of JS runtimes instead of exploitations of XSS bugs in webkit.
- marshray 14y agoThat's the thing about Javascript. The tiniest little XSS or subtle origin violation results in the entire browser app being 100% 'pwned' (to use the technical term). The pwnage can even persist into the future for that user when you consider the ability of browsers to cache content and HTML5's data store.