Issue metadata
Sign in to add a comment
|
no security implementation of client side open redirection
Reported by
rakesh6...@gmail.com,
Apr 18 2017
|
||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 UBrowser/6.1.2015.1007 Safari/537.36 Steps to reproduce the problem: 1. open the crome browser and go to gmail.com@facebook.com 2. now it will be redirected to the facebook.com and leads to the open redirecion,this is because no browser security implementation in the chrome browser and with this many websites are vulnerable to this type of attack What is the expected behavior? What went wrong? scenario 1.lets take a website as http://test.com/cD.do?targetURL=https://google.com 2.and the website is using some mechanism and it doesnot redirect into the google.com and shows as http://test.comhttps://google.com 3.now if we keep @google.com in the targetURL=@google.com now it will be redirected to the google.com in between this the url will be converted like test.com@google.com,here any website after "@"is treated as actual website and this leads to open redirection 4.as like protection for xss their should be some security implementation for open redirection also in the chrome browser 5.for the clear understanding i have found a website to show the redirection Did this work before? N/A Chrome version: 57.0.2987.133 Channel: n/a OS Version: 10.0 Flash Version:
,
Apr 19 2017
,
Jul 26 2017
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by mea...@chromium.org
, Apr 19 2017