Re:Google's login page accepts a vulnerable GET parameter
by woliveirajr on Tuesday August 30, 2016 @10:52PM
(#12395662)
Perfect example. Everything that I can see in my cell looks right, including informations from the green padlock, just opening (and understanding! ) the whole URL would make one NOT enter the password.
Re:Google's login page accepts a vulnerable GET parameter
by kuschku on Tuesday August 30, 2016 @11:05PM
(#12395721)
And that’s the thing, thanks to Let’s Encrypt, the padlock on the fake site also stays, everything looks normal.
If you now also register something like accountsgoogle.com or a similar page, people likely wouldn’t even notice.
This is like it’s made for phishing.
Re:Google's login page accepts a vulnerable GET parameter
by ascorbic on Wednesday August 31, 2016 @06:08AM
(#12397202)
Ironically, Chrome is now blocking that as a phishing site!
Re:Google's login page accepts a vulnerable GET parameter
by kuschku on Wednesday August 31, 2016 @07:31AM
(#12397485)
Yes, and now I have to deal with Google to unblock it.
One of the reasons why I hate automated systems judging things.
Thanks, Google...
Re:Google's login page accepts a vulnerable GET parameter
by mentat on Wednesday August 31, 2016 @12:04PM
(#12399302)
Please tell me this is sarcasm. The system is working...
Re:Google's login page accepts a vulnerable GET parameter
by kuschku on Wednesday August 31, 2016 @01:53PM
(#12400148)
The system would be working if it was an actual phishing page.
If it is an example, which is non-malicious, and even says "Don’t enter your password", and doesn’t even store the data from the input fields, it’s not.
It could easily check if any JS is executed, or if the form fields ever get sent anywhere (both is not the case).
Re:Google's login page accepts a vulnerable GET parameter
by peteretep on Wednesday August 31, 2016 @06:32AM
(#12397278)
The only bit you're missing here is redirecting the user back to a Google page you do need to be logged in for, so they think everything is ok and don't think twice about what just happened
Re:Google's login page accepts a vulnerable GET parameter
by kuschku on Wednesday August 31, 2016 @07:37AM
(#12397504)
I was hoping I could avoid getting flagged as phishing site if I'd make the form ignore all content and redirect back here.
Turns out I was wrong.
Re:Google's login page accepts a vulnerable GET parameter
by woliveirajr on Wednesday August 31, 2016 @11:52AM
(#12399197)
Temporary: please take the page back, it worked for me... Keep the video for those who can't.
Re:Google's login page accepts a vulnerable GET parameter
by kuschku on Wednesday August 31, 2016 @02:15PM
(#12400291)
I can’t, it’s hard already to get rid of the phishing flag Google has set for the domain.
Re:Google's login page accepts a vulnerable GET parameter
by gyey on Tuesday August 30, 2016 @10:58PM
(#12395694)
This is what I get: "Sorry, this page is not valid AMP HTML"
Re:Google's login page accepts a vulnerable GET parameter
by kuschku on Tuesday August 30, 2016 @11:00PM
(#12395702)
Do you happen to be on mobile? This particular site only works on desktop, at the moment. I’ll do a screenrecording for you mobile users in a moment.
Re:Google's login page accepts a vulnerable GET parameter
by gyey on Tuesday August 30, 2016 @11:23PM
(#12395794)
Yes, I'm on mobile. That must be it.
(link removed, see video below)
And tell me your parents/grandparents/etc will not mistake that for the real thing.
(you can enter whatever you want into the phishing form, it will just take you back to this post – but someone with less morals could do entirely different things)
EDIT: Video for mobile users (this page doesn’t work on mobile): https://cdn.kuschku.de/ServiceLogin/video.mp4