Re:Using the HTML5 Fullscreen API for Phishing Attacks
by jpxxx on Tuesday October 09, 2012 @01:57AM
(#4630190)
Yeah, that's all I've got. The only scenario protecting the unsophisticated here is that the malicious javascript (presumably) has to be delivered from some domain, and domain filtering is in full effect almost everywhere.
This API means that if a malicious JS can be executed, it's game over for a number of defenses that only communicate visually.
Re:Using the HTML5 Fullscreen API for Phishing Attacks
by ricardobeat on Tuesday October 09, 2012 @05:28AM
(#4630668)
The domain where this is hosted would get added to the blacklist pretty quickly too.
I imagine all of the payload (save for the return trip) could be put into innocent looking client-side Javascript, but that doesn't get around the fact that someone's still got to serve the JS...