Live data from Hacker News

Hundreds of exposed Amazon cloud backups found leaking sensitive data

techcrunch.com

1–10 of 73 posts

Re: Hundreds of exposed Amazon cloud backups found leaking sensitive data

#2
Public EBS snapshots are great, and thankfully a design other clouds didn't copy. I've found all kinds of stuff in there, including a 900GB Oracle backup of a publicly traded manufacturer's accounting system. It doesn't require much imagination to understand how this kind of data could be profited from, given relatively low effort

It seems unlikely a lot of people didn't already know about this, it's hard to miss even if you only spend a few days with the EC2 API, and it's also quite surprising AWS have yet to correct the design. 90% chance it is mostly a UI problem -- there are no warning labels around snapshotting in the EC2 UI

Re: Hundreds of exposed Amazon cloud backups found leaking sensitive data

#5
I've been working almost exclusively in the AWS space for about 10 years now. Clients anywhere from tiny little three-person consultancies to Fortune 100. Commercial, govcloud, dozens of clients.

Never once have I ever found a use case for making public EBS snapshots.

Who on Earth is thinking that it is a good idea to take an EBS snapshot and make it public?

Note, several of those engagements did involve multiple accounts, and the need to share / copy AMIs and/or snapshots between accounts. But never making them public.

Re: Hundreds of exposed Amazon cloud backups found leaking sensitive data

#6
post #4

It’s still true that most security issues are caused by human ineptitude, not clever vulnerability-hunting or burning sophisticated zero-days.

I would replace "human ineptitude" with "flawed system design that makes it very easy to make very bad mistakes"

Re: Hundreds of exposed Amazon cloud backups found leaking sensitive data

#7
post #6
post #4

It’s still true that most security issues are caused by human ineptitude, not clever vulnerability-hunting or burning sophisticated zero-days.

I would replace "human ineptitude" with "flawed system design that makes it very easy to make very bad mistakes"

That's a valid way to categorize all memory errors in C.

Re: Hundreds of exposed Amazon cloud backups found leaking sensitive data

#8
post #2

Public EBS snapshots are great, and thankfully a design other clouds didn't copy. I've found all kinds of stuff in there, including a 900GB Oracle backup of a publicly traded manufacturer's accounting system. It doesn't require much imagination to understand how this kind of data could be profited from, given relatively low effort It seems unlikely a lot of people didn't already know about this, it's hard to miss eve…

How do you scour for EBS snapshots and open browsable S3 buckets?

Re: Hundreds of exposed Amazon cloud backups found leaking sensitive data

#9
post #5

I've been working almost exclusively in the AWS space for about 10 years now. Clients anywhere from tiny little three-person consultancies to Fortune 100. Commercial, govcloud, dozens of clients. Never once have I ever found a use case for making public EBS snapshots. Who on Earth is thinking that it is a good idea to take an EBS snapshot and make it public? Note, several of those engagements did involve multiple acc…

> Who on Earth is thinking that it is a good idea to take an EBS snapshot and make it public?

Non-marketplace AMIs are built on public EBS snapshots, but that's something they should still fix. Marketplace AMIs already handle private snapshots

Re: Hundreds of exposed Amazon cloud backups found leaking sensitive data

#10
post #2

Public EBS snapshots are great, and thankfully a design other clouds didn't copy. I've found all kinds of stuff in there, including a 900GB Oracle backup of a publicly traded manufacturer's accounting system. It doesn't require much imagination to understand how this kind of data could be profited from, given relatively low effort It seems unlikely a lot of people didn't already know about this, it's hard to miss eve…

How do you scour for EBS snapshots and open browsable S3 buckets?

For EBS, step 1 is reading the docs, step 2 is cutpasting a documentation example.

For S3 I'm not sure how people are building their lists. AFAIK the API provides no enumeration. So this is possibly something coming from web crawl data (e.g. common crawl)

Post reply on HN