{"id":1939,"date":"2025-02-14T11:58:04","date_gmt":"2025-02-14T11:58:04","guid":{"rendered":"https:\/\/cybersecurityinfocus.com\/?p=1939"},"modified":"2025-02-14T11:58:04","modified_gmt":"2025-02-14T11:58:04","slug":"whoami-name-confusion-attacks-can-expose-aws-accounts-to-malicious-code-execution","status":"publish","type":"post","link":"https:\/\/cybersecurityinfocus.com\/?p=1939","title":{"rendered":"whoAMI name confusion attacks can expose AWS accounts to malicious code execution"},"content":{"rendered":"
\n
\n
\n
\n
<\/div>\n

Thousands of active AWS accounts are vulnerable to a cloud image name confusion attack that could allow attackers to execute codes within those accounts.<\/p>\n

According to DataDog research, vulnerable patterns exist in the way multiple software projects retrieve Amazon Machine Image (AMIs) IDs to create Amazon elastic compute cloud (EC2) instances.<\/p>\n

\u201cThe vulnerable pattern allows anyone that publishes an AMI with a specially crafted name to gain code execution within the vulnerable AWS account,\u201d the researchers said in a blog post. \u201cIf executed at scale, this attack could be used to gain access to thousands of accounts.\u201d<\/p>\n

<\/a>The whoAMI attack<\/h2>\n

Researchers have demonstrated that the attack vector \u201cwhoAMI\u201d can impact many private and open-source code repositories. Over 10,000 AWS accounts are vulnerable to this attack, about 1% of the reported one million active<\/a> AWS deployments.<\/p>\n

The whoAMI attack is a name confusion exploit, a type of supply chain attack<\/a> where misconfigured software is tricked into using a malicious resource. Unlike the dependency confusion attacks<\/a>, which targets software dependency like pip packages<\/a>, whoAMI involves a rogue virtual machine image impersonating a legitimate one.<\/p>\n

An AMI is a pre-configured virtual machine template used to launch EC2 instances in AWS. It includes the OS, software, and configurations. Users can specify a known AMI ID or search for the latest public AMIs using the ec2.DescribeImgaes API to find region-specific options.<\/p>\n

If the \u201cowners\u201d attribute is omitted when searching for an AMI, the researchers noted<\/a>, AWS may return results that include public community AMIs from any account. Attackers can exploit this by publishing a malicious AMI with a matching name and newer timestamp, tricking automated infrastructure-as-Code (IaC) tools like Terraform into selecting a compromised image.<\/p>\n

Victims are vulnerable only if they use the ec2.DescribeImages API with a name filter, omit the \u201cowners\u201d attribute, and select the most recent AMI, increasing the risk of deploying a compromised instance.<\/p>\n

<\/a>Amazon fixed the problem<\/h2>\n

Through the AWS Vulnerability Disclosure Program (VDP), researchers found that AWS\u2019s own internal non-production systems were vulnerable, potentially allowing attackers to execute code within AWS infrastructure. The issue was disclosed<\/a> and promptly fixed in September 2024.<\/p>\n

A little later on December 1, 2024, AWS introduced Allowed AMIs<\/a>, a feature that lets users define a trusted allow list for AMI selection, mitigating the whoAMI name confusion attack.<\/p>\n

The blog post included a list of queries developers can use to identify risky patterns in their code, along with a link to the open-source tool, whoAMI-scanner<\/a>, for detecting untrusted AMIs in customer environments.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"

Thousands of active AWS accounts are vulnerable to a cloud image name confusion attack that could allow attackers to execute codes within those accounts. According to DataDog research, vulnerable patterns exist in the way multiple software projects retrieve Amazon Machine Image (AMIs) IDs to create Amazon elastic compute cloud (EC2) instances. \u201cThe vulnerable pattern allows […]<\/p>\n","protected":false},"author":0,"featured_media":1940,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1939","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-education"],"_links":{"self":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts\/1939"}],"collection":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1939"}],"version-history":[{"count":0,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts\/1939\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/media\/1940"}],"wp:attachment":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1939"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1939"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1939"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}