+- Hack Forums (https://hackforums.net)
+-- Forum: Hacks, Exploits, and Various Discussions (https://hackforums.net/forumdisplay.php?fid=45)
+--- Forum: Grayhat • Purple Team • Hybrid Security (https://hackforums.net/forumdisplay.php?fid=449)
+---- Forum: Website Hacking (https://hackforums.net/forumdisplay.php?fid=43)
+---- Thread: Bypassing chromes xss audit (/showthread.php?tid=5644803)
Bypassing chromes xss audit - vorticalbox - Jun 12, 2017
I have found a website with a xss but if using any chrome based browser the xss detection kicks in and blocks the attack.
Any one have any tips how to by pass it? Firefox,ie etc. Work fine.
* - Lord - Jun 12, 2017
Not using Chrome seems like a good start.
* - vorticalbox - Jun 12, 2017
(Jun 12, 2017 12:16 AM)That One Random Wrote: Not using Chrome seems like a good start.
Yeah that's one idea but I cant know what the user will be using and this want to maximise victims.
* - ๖ۣۜCriminal - Jun 12, 2017
(Jun 12, 2017 12:41 AM)vorticalbox Wrote: Yeah that's one idea but I cant know what the user will be using and this want to maximise victims.
https://hackforums.net/showthread.php?tid=5472183
can do something like this to maximize targets^ with a little SE you can force them to use another browser like firefox for example whch if it detects their on the correct browser will redirect them to the payload.
* - vorticalbox - Jun 12, 2017
(Jun 12, 2017 01:03 AM)๖ۣۜCriminal Wrote: can do something like this to maximize targets^ with a little SE you can force them to use another browser like firefox for example whch if it detects their on the correct browser will redirect them to the payload.
Thanks for the idea didn't think of that :)
* - ๖ۣۜCriminal - Jun 12, 2017
(Jun 12, 2017 01:41 AM)vorticalbox Wrote: Thanks for the idea didn't think of that :)
in hacking the skys the limit.
* - pop.pop.ret - Jun 12, 2017
It's currently possible to bypass Chrome's XSS filter and various CSP configurations via an SWF assuming that your victim has flash enabled. PM me for more info.
Or alternatively you could just go find a universal bypass for chrome :) not too difficult.
Also, depending on what context the reflection to source is (for example whether its inline, tag-based or w/e) can massively effect how easy it is to come up with a bypass. If its inline injection e.g. its being reflected as an attribute within a hidden input tag or something then I can give you a working bypass for this too.
Just gimme the context, show me the reflection point and how its landing in the source.. and maybe I can help.