13 ms·
....Sounds like an awesome opportunity to fuzz that API, and dump the entirety of Google's "compromised credential" DB. For research purposes only of course. I
by salawat 4y ago
....Sounds like an awesome opportunity to fuzz that API, and dump the entirety of Google's "compromised credential" DB.
For research purposes only of course. I'm sure they provisioned enough instance to handle a rather aggressive fuzzing as well seeing as this thing is surely built to stand up to the entire Chrome using internet logging in at the same time, right?
And surely there is no way whatsoever one could use this data to potentially compromise other accounts...
Or use it as a basis for birthday attacks on unreported compromised accounts. Or, set up some unique credentials in compromised systems, then checking the googleapi call for it to see if the intrusion has been reported/caught yet.
Ahhhh side channels. Yes, side channels. Fnord.
- mpeg 4y agoIf you look at the link provided by this thread’s parent you’ll see the credential database / API is encrypted, and the input is 3 bytes of the username hash. None of what you’re describing is possible. Even if it was, it would not be as useful as you think as the only leaks in that database will be public leaks that everyone can easily find if they know where to look.
- worldsavior 4y agoThose leaked passwords are already in the internet. And even if they're aren't (then they are not leaked), yes, go brute force google api.