3 ms·
Chris Vickery (who discovered this problem) has quite a record of discovering unsecured S3 buckets. How does he do it?
by nl 9y ago
Chris Vickery (who discovered this problem) has quite a record of discovering unsecured S3 buckets.
How does he do it?
- skywhopper 9y agoS3 buckets have a single unified namespace, so presumably he's got bots running 24/7 scanning every legal bucket name. Filter it down using english words, likely ops jargon, and company names. I'm guessing Accenture has lots of buckets named "accenture-prod-uploads" or other promising combinations.
- graystevens 9y agoYup, they must have (except for one region in AWS), a DNS compliant and completely unique name. So it’s just a case of dns bruteforce, working through wordlists and common phrases/words to try and spot them. I ran something very similar for a couple of months, and found >200,000 valid S3 buckets, a large portion of which had permissions issues (public list etc).
- numbsafari 9y ago... and this is why I generally prefix all bucket names with a UUID. Mildly user hostile, but bucket names go in config files, so who cares?
- ams6110 9y agoAnd if he's doing it, others are too. There's a very high likelihood that all this data has been compromised.
- stephengillie 9y agoI wrote a web-scraping script to iterate through buckets and download items, to see which of my employer's S3 buckets were unsecured. Chris probably did the same thing, but is spidering the whole namespace instead of just targeting a known list. S3 has a hostile interface which is missing many necessary features. AWS try to supplement this through 3rd party products (Cloudberry) and other paid services (Macie), instead of making a client that helps you know what's in your buckets and who can see them.
- jon_richards 9y agoIf I recall correctly, you can't specify on a bucket that you want a group to access it. You have to specify on the group that it has access to the bucket. There's tons of stupid shit like that.
- stephengillie 9y agoJust an hour ago I was on a call, helping someone else find a file she had just uploaded, but wasn't visible in the S3 Web Console. Because it doesn't bring back ALL files in the folder, just the current 300. And they aren't sorted, so the file she had just uploaded was 2 pages back from a lot of other files which were uploaded today. It's nonsensical.