July 10th, 2024

Well, it's just an AWS Account ID

AWS Account IDs are crucial for cloud security, aiding in resource sharing and reconnaissance. They facilitate IAM entity enumeration, service discovery, and security testing, highlighting AWS footprint insights for potential attacks. An upcoming course on securing AWS environments is recommended.

Read original articleLink Icon
Well, it's just an AWS Account ID

The article discusses the significance of AWS Account IDs in the context of cloud security. It explains that these 12-digit identifiers are crucial for resource sharing within and outside AWS accounts. The piece highlights how knowing an Account ID can aid in enumerating IAM entities, discovering services in use, finding public resources, correlating leaked resources, and evading detection. Real-world examples and tools like validate_iam_principals.py and Trufflehog are mentioned to demonstrate the practical implications of leveraging Account IDs for reconnaissance and security testing. The author emphasizes that while Account IDs themselves may not pose a direct security risk, they play a vital role in facilitating various cloud attacks by providing insights into an organization's AWS footprint. The article concludes by promoting an upcoming course on securing AWS environments to prevent unintended exposure of resources and enhance overall security posture.

Related

Simple ways to find exposed sensitive information

Simple ways to find exposed sensitive information

Various methods to find exposed sensitive information are discussed, including search engine dorking, Github searches, and PublicWWW for hardcoded API keys. Risks of misconfigured AWS S3 buckets are highlighted, stressing data confidentiality.

WikiLeaks – Amazon Atlas (2018)

WikiLeaks – Amazon Atlas (2018)

WikiLeaks leaked Amazon's 2018 document detailing global data centers, including CIA ties and AWS Secret Region. Amazon leads cloud market, vies for $10B Pentagon contract. WikiLeaks turns data leak into awareness game.

ID verification service for TikTok, Uber, X exposed driver licenses

ID verification service for TikTok, Uber, X exposed driver licenses

A cybersecurity researcher found AU10TIX's admin credentials exposed online, risking data breach for TikTok, Uber users. Concerns rise over ID verification services' vulnerability to cyberattacks, emphasizing the need for enhanced security measures.

Identity Verification Used by X, TikTok, and Uber Exposed Driver's Licenses

Identity Verification Used by X, TikTok, and Uber Exposed Driver's Licenses

An identity verification firm, AU10TIX, exposed login credentials, risking access to sensitive data like driver's licenses. Despite claims of prompt revocation, functional credentials were found. AU10TIX partners with major platforms.

Eight versions of UUID and when to use them

Eight versions of UUID and when to use them

The article covers eight versions of UUIDs, detailing their characteristics and best use cases. Recommendations include v4 for random IDs, v7 for sortable IDs, and v5 or v8 for custom data. Some versions have been replaced. The author shares insights and hints at a secretive project.

Link Icon 10 comments
By @christina97 - 6 months
This seems wrong. Surely you can’t “Enumerate IAM Entities” with just the aAccount ID?

So if a company has a user for every dev with username first.last, you could list all devs just by knowing the Account ID?

Maybe the author misunderstood what “enumerate” means and meant to say that you can check if a given IAM entity exists under the account? Enumeration and bruteforce are very different things.

By @mikeweiss - 6 months
Nice article. For those interested here is a project listing companies who's AWS account IDs are known (generally because the IDs have been publicly disclosed by the company itself for product integration purposes)

https://github.com/fwdcloudsec/known_aws_accounts

By @weinzierl - 6 months
Relevant talk how you can discover the AWS Account ID of any S3 bucket: https://pretalx.com/fwd-cloudsec-2024/talk/9FRYE9/
By @nikolay - 6 months
I consider anything that's not public knowledge to be a secret. When possible, try not to come up with anything that's guessable. I randomize even DB usernames in Terraform, not just the passwords. I do the same with schema names, etc. This requires sweat and tears, but it's always worth it. WordPress sucks, but the idea to have a custom table name prefix is not random, but a security consideration. But don't prefix field names the same way, please! :D
By @baol - 6 months
Not an expert on AWS, but as this seems something that you may need to share and that cannot be easily changed, considering it a secret is just snake oil.
By @rollulus - 6 months
This briefly mentions something I’ve seen during work and never dared to explore: the various public (RDS) snapshots. Oh boy, some people either use very realistic test datasets or they accidentally made things public that shouldn’t be at all.
By @Narkov - 6 months
So many words and FUD...with the bottom line being...

> Here's my take: The Account ID is useless and not a direct weakness.

By @ghusto - 6 months
FUD, don't waste your time.