34 ms·
It's not a bug. It is either a backdoor placed there from the design/implementation or super lazy programming. I don't want to think it's done on purpose (Hanlo
by HenryBemis 6y ago
It's not a bug. It is either a backdoor placed there from the design/implementation or super lazy programming. I don't want to think it's done on purpose (Hanlon's razor).
- chki 6y agoIf that's an intentional backdoor it's a very weird backdoor. Wouldn't you at least obfuscate things a little bit? Simply mixing up the characters in that string in some pre-planned order would be enough.
- wyattpeak 6y agoWhile I doubt it's an intentional backdoor, I wouldn't assume that backdoors would be obfuscated. You can't deny knowledge of an obfuscated backdoor, while an obvious one could plausibly be a simple mistake.
- joosters 6y agoIf you stick with that logic, you’ll think every mistake is a backdoor !
- BHSPitMonkey 6y agoIf it were a malicious backdoor, it wouldn't have been "hidden" in the response to the _actual_ password reset request form.
- franga2000 6y agoA full account takeover is a really shitty backdoor. Just make a separate "test" endpoint that's exactly the same as the main API but requires no authentication so anyone can read anything. Perfectly deniable as just a bug and entirely undetectable from a target's POV.