high
AWS Default Roles Can Lead to Service Takeover
Published Tue, Apr 29th, 2025
Platforms
Research uncovered security flaws in default AWS service roles, granting overly broad permissions like full S3 access. This allows privilege escalation, cross-service access, and potential account compromise across services like SageMaker, Glue, and EMR. Attackers could exploit these roles to manipulate critical assets and move laterally within AWS environments. AWS has since updated default policies and documentation to mitigate risks.
SageMaker, Glue, EMR, CloudFormation, CDK
Audit existing IAM roles and remove overly permissive policies like AmazonS3FullAccess. Restrict S3 access to only specific required buckets for each service role. Regularly review and enforce least privilege access across all AWS services.
No tracked CVEs
Contributed by https://github.com/korniko98
Entry Status
Stub (AI-Generated)
Disclosure Date
-
Exploitability Period
Known ITW Exploitation
Detection Methods
Monitor for suspicious S3 access patterns or modifications to service-specific buckets. Audit IAM roles for overly broad permissions, especially full S3 access. Use AWS CloudTrail to detect unauthorized actions across services.
Piercing Index Rating
Discovered by
Yakir Kadkoda, Ofek Itach, Aqua Security
high
Tenable discovered a privilege escalation vulnerability in Google Cloud Platform's Cloud Composer service, dubbed ConfusedComposer. It allowed users with composer.environments.update permission to ...
Varonis Threat Labs discovered a vulnerability in Azure SQL Server allowing privileged users to create malicious firewall rules that can delete Azure resources when triggered by admin actions. The ...
A path traversal vulnerability in AWS SSM Agent's ValidatePluginId function allows attackers to create directories and execute scripts in unintended locations on the filesystem. This could lead to ...