Re:We Hacked Burger King: How Auth Bypass Led to Drive-Thru ...
by siffin on Saturday September 06, 2025 @03:33PM
(#45152212)
It could never be anywhere near as irresponsible as the original bad security practices, though. At some point, if you wanna make money by handling people's sensitive data, you are the responsible party, not everyone else.
Re:We Hacked Burger King: How Auth Bypass Led to Drive-Thru ...
by saagarjha on Saturday September 06, 2025 @03:30PM
(#45152197)
Are you in a position to hire security engineers?
Re:We Hacked Burger King: How Auth Bypass Led to Drive-Thru ...
by 93po on Saturday September 06, 2025 @03:28PM
(#45152177)
users at large have a right to know if their data is being handled recklessly by any person or group, and just because some entity has arbitrary rules and poor communication/practices on how they want to tell them disclosures, it doesn't in any way make it irresponsible to let the public know: hey, your shit is getting recorded and is available for anyone to download and listen to.
Re:We Hacked Burger King: How Auth Bypass Led to Drive-Thru ...
by Retric on Saturday September 06, 2025 @05:04PM
(#45152813)
Some companies will keep systems vulnerable indefinitely. If a company hasn’t fixed the issue in a year, public disclosure is likely a better option than doing nothing.
Re:We Hacked Burger King: How Auth Bypass Led to Drive-Thru ...
by kevincox on Saturday September 06, 2025 @06:29PM
(#45153486)
Yes, that is why responsible disclosure almost always comes with deadlines. You give the chance for the company to resolve the issue and mitigate user impact. But if they are taking so long that the user impact will be higher than you just disclose.
Re:We Hacked Burger King: How Auth Bypass Led to Drive-Thru ...
by akerl_ on Saturday September 06, 2025 @10:36PM
(#45154882)
What if your assessment is that the user impact is already high enough that the right time to disclose is immediately?
Re:We Hacked Burger King: How Auth Bypass Led to Drive-Thru ...
by kevincox on Sunday September 07, 2025 @06:55AM
(#45157089)
If you assess that the best time to publicly disclose is immediately then disclose immediately.
But I find that this case is rare. Typically it would be something like many of the following being met:
- It is likely to be discovered by an attacker soon.
- History shows that the company is unlikely to fix it soon.
- Users have some way to protect themselves.
- Your disclosure is likely to reach a significant number of users.
Re:We Hacked Burger King: How Auth Bypass Led to Drive-Thru ...
by akerl_ on Sunday September 07, 2025 @07:38AM
(#45157323)
How do you know it hasn’t been discovered by another attacker already?
Re:We Hacked Burger King: How Auth Bypass Led to Drive-Thru ...
by ranger_danger on Tuesday September 09, 2025 @02:07PM
(#45185930)
You don't, but you make a judgement call based on different criteria, such as how difficult the issue was to find, maybe how popular/big the site is, etc., as to whether or not you think anyone else is likely to know about it already.
Even the most security-aware companies have a process to fix vulnerabilities, which takes time.
I would never hire someone that doesn't reaponsibly coordinate with the vendor. In most cases it's either malicious or shows a complete lack of good judgement.
In the case of bobdajrhacker? Both.