Many cloud services ask customers to create an AWS role that the vendor’s own AWS account is allowed to use. It is a standard and convenient way to give a vendor access. Between 14 and 26 October, an attacker used IAM credentials from an AWS account associated with data platform vendor Qubole to use those roles in several customers’ environments. The activity was investigated by Wiz, Sentra and Mandiant, and Wiz published details on 9 November.
What the attacker did
- Assumed the trusted Qubole roles in multiple customer AWS accounts. In most cases, nobody else had used those roles that month.
- Listed storage, compute, databases and security settings.
- Downloaded data from any S3 bucket the roles could reach, in some cases entire buckets.
- Collected secrets from Lambda environment variables, Secrets Manager and Parameter Store, then tested them against AWS, Microsoft Entra ID and Okta.
Separately, from 8 October, customer-owned access keys created for Qubole integrations were also tested, and a small number of customer environments were compromised that way. How the attacker obtained the Qubole credentials has not been disclosed.
Why it matters
Vendor roles are often created during a trial or project, given wide permissions and then forgotten. They carry the vendor’s trust long after anyone remembers why they exist. If the vendor is compromised, so are you.
What to do
- List every IAM role that trusts an external account, and delete the ones you no longer use.
- Cut permissions to the minimum, especially broad S3 read, Secrets Manager and Parameter Store access.
- Restrict where roles can be used from, with source IP or VPC endpoint conditions where the vendor supports them.
- Alert on vendor role use from new networks, VPNs or hosting providers, and keep CloudTrail enabled across the organisation.
- If you used Qubole, review CloudTrail from 1 October for the indicators Wiz published, and rotate every secret the roles could read. Revoke active sessions too, because rotating credentials does not end sessions already issued.
Sources: Wiz: Qubole cross-account access abused in the wild; SecurityWeek: over a dozen organisations hit in Qubole supply chain attack.