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?
[ Parent
| on HN ]
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.