Will it make it easier to identify the operators of malvertising campaigns hosted on AWS?
How to find the AWS account ID of any S3 bucket
71–80 of 227 posts
Re: How to find the AWS account ID of any S3 bucket
#72Re: How to find the AWS account ID of any S3 bucket
#73Earlier quoted context omitted.
That's the part that surprised me as well; it doesn't seem like a field that should be eligible for anything other than an exact match. I am unable to conceive of a use case for pattern matching account IDs.
If for some reason you’re dealing with thousands of accounts that are architecturally indistinguishable, bucketing them by ID prefix isn’t a particularly wild thing to want to do.
Re: How to find the AWS account ID of any S3 bucket
#74Earlier quoted context omitted.
That's the part that surprised me as well; it doesn't seem like a field that should be eligible for anything other than an exact match. I am unable to conceive of a use case for pattern matching account IDs.
Well, that assumes that the ID is cryptographically random. Perhaps that is a bad assumption.
Odds are that an account wildcard match like 676363687* will just match a few hundred entirely random AWS accounts.
Re: How to find the AWS account ID of any S3 bucket
#75Earlier quoted context omitted.
If for some reason you’re dealing with thousands of accounts that are architecturally indistinguishable, bucketing them by ID prefix isn’t a particularly wild thing to want to do.
At that point you should be using AWS Organizations and OUs.
Re: How to find the AWS account ID of any S3 bucket
#76> The ability to apply a wildcard match on the s3:ResourceAccount condition key That’s the crazy part. No good can ever come from this - there is no legitimate reason why you would grant or deny permission based on a partial account id match.
As it is my side project’s side project I do what is easy so these operators are always available even in cases where they don’t make sense (I dunno what happens if you try a regex query on a number, I don’t care) I can imagine there is something a bit like this inside AWS but for a security-sensitive system with a lot of users you have a different standard.
Re: How to find the AWS account ID of any S3 bucket
#77aws s3 bucket needs to match the domain for website hosting. let's say if apple uses s3, they need to create bucket name "apple.com", and then we can find what aws account which apple is using.
This is outdated information, and not required anymore when using CloudFront.
And even in the past, you could use the S3 API to implement a reverse proxy without matching bucket and domain names.
Re: How to find the AWS account ID of any S3 bucket
#78Re: How to find the AWS account ID of any S3 bucket
#79How might this matter? A obvious one: Given a production bucket, it’s now possible to find development buckets for that same org, which is not expected behavior IMO.
Re: How to find the AWS account ID of any S3 bucket
#80> While account IDs, like any identifying information, should be used and shared carefully, they are not considered secret, sensitive, or confidential information. https://docs.aws.amazon.com/accounts/latest/reference/manage...
If they're not secret, sensitive, or confidential, then why must they be shared carefully?