Re:Google's login page accepts a vulnerable GET parameter
by tptacek on Tuesday August 30, 2016 @11:46PM
(#12395887)
I feel like at this point we both understand the point I was making and don't need to litigate it further. You can and should feel free to disagree with it, but there's a reason pentesters file open redirects sev:lo.
(XSS is the canonical sev:medium, for what it's worth).
Re:Google's login page accepts a vulnerable GET parameter
by throwaway5752 on Wednesday August 31, 2016 @12:00AM
(#12395934)
x
Re:Google's login page accepts a vulnerable GET parameter
by ebbv on Wednesday August 31, 2016 @12:16AM
(#12395988)
Man if you are afraid to disagree with someone just because of who they are I feel bad for you. I've let pg have it on here when I disagreed with him. It doesn't matter. Everybody's wrong sometimes.
If you're saying that you meant the mainstream of security professionals specifically, I'd be interested in what a survey of security professionals had to say about open redirect. For me it's clearly a potential attack vector, and Google's specific implementation is obviously sloppy and lazy. I can't see any security professional worth their salt giving it a pass.
As far as Google not being a running joke, that's true and it's all the more reason it's surprising they are so dismissive of concerns about their way too broad whitelist.