2 ms·
It’s a reasonable theory but step one required to trigger this bug is an unauthenticated request. It’s unclear if their logs indicated that or they got lucky tr
by vlovich123 6y ago
It’s a reasonable theory but step one required to trigger this bug is an unauthenticated request. It’s unclear if their logs indicated that or they got lucky trying to repro that someone thought to try with an unauthenticated request first when the back to back session didn’t repro.
- whimsicalism 6y agoFrom the writeup, it sounds like the latter, but we obviously can't be sure.
- aidos 6y agoCould be that there’s some tell tale in the logs. We recently fixed a bug with incomplete requests by noticing in nginx logs that the size of the headers + the size of the body was the size of the buffer of a linux socket.