3 ms·
Do we? "Some user data exposed on AWS due to crappy S3 permissions" happens like forty times a year. People publish papers annually just finding stupid crap lik
by UncleMeat 8y ago
Do we? "Some user data exposed on AWS due to crappy S3 permissions" happens like forty times a year. People publish papers annually just finding stupid crap like this in mobile apps. Misconfiguration bugs happen in thousands upon thousands of products. Where do we lose our minds?
- Brockenstein 8y agoWhen it makes headline news... typically.
- UncleMeat 8y agoLess than 1% of these make the news. Papers regularly find tens of thousands of examples of this vuln.
- emn13 8y agoThere is a qualitative difference between an internally discovered vulnerability - presumably by somebody with lots of access, knowledge, and the ability to verify their hypotheses - and an externally discovered vulnerability. Furthermore, if every potential vulnerability that might have been exploited needs to be reported as a breach... then each and every bug in any library and other dependency you use likely needs a breach report too - after all, you typically cannot verify retrospectively whether that exploit wasn't independently discovered and abused before the fix. I'm not even positive such a reporting requirement would really be a bad idea, but it would definitely needs some more mature reporting and population education to tell the two classes of issue apart, especially since it's pretty vague where you draw the line on what needs publication once you get that far.