4 ms·
This one was good too, especially because the screenshot definitely gave many some heart palpitations. https://opnsec.com/2018/07/into-the-borg-ssrf-inside-goo
by jchw 7y ago
This one was good too, especially because the screenshot definitely gave many some heart palpitations.
https://opnsec.com/2018/07/into-the-borg-ssrf-inside-google-production-network/ https://opnsec.com/2018/07/into-the-borg-ssrf-inside-google-...
- saagarjha 7y agoThat's a lot of internal information. I'm not sure I'd be comfortable publishing that, even if the company was friendly to security researchers.
- jchw 7y agoI think if I were an outsider I would’ve probably gotten pretty shy just after discovering an internal SSRF at a big corp. However, that also probably explains why I am not a security researcher.
- jotm 7y agoAm I reading this right? 13,337 for a unrestricted file access vulnerability? Seems rather cheap, I think even other interested parties would pay more :/
- jchw 7y agoIt was treated as an unrestricted file access vulnerability. I don’t want to accidentally disclose any non-public information (as an employee of Google) so I’ll just say I suspect there wasn’t really a ton more to see other than status and debug pages. Not to downplay the value of such a vulnerability, just saying that with defense-in-depth risks like this should be relatively well contained. It sounds like they got access to some confidential operational information but were nowhere near user data, and there was no obvious path to get there without much worse vulnerabilities.