Phying News
P非影 中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Using Azure Automation Accounts to Access Key Vaults

netspi.com | blog | #cloud | #secrets | #privilege-escalation | #azure | #cloud-pentesting | #key-vault | #automation-accounts | #runbook

Summary

Karl Fosaaen shows how Contributor access to Azure Automation Accounts can be abused by modifying runbooks to dump secrets from Key Vaults, enabling attackers to read vault data without Owner rights.
Published
Collected

original ↗

Related coverage

blog · netspi.com
Get-AzurePasswords: A Tool for Dumping Credentials from Azure Subscriptions
Karl Fosaaen introduces Get-AzurePasswords, a MicroBurst script that automates credential dumping from Azure Key Vaults, App Services configurations, and Automation Accounts via Azure PowerShell.
blog · netspi.com
Lateral Movement in Azure App Services
From command execution on an Azure App Services host, attackers can inspect the environment, reach storage and Azure SQL, and abuse Managed Identity tokens to access Key Vaults and escalate.
blog · netspi.com
Maintaining Azure Persistence via Automation Accounts
NetSPI shows how attackers can persist in Azure after privilege escalation using Automation Accounts, privileged runbooks, and webhook triggers that restore Owner access with a single POST request.
blog · netspi.com
Get-AzurePasswords: Exporting Azure RunAs Certificates for Persistence
Karl Fosaaen starts an Azure Automation series, showing how runbook permissions allow attackers to export RunAs certificates and credentials for maintaining privileged access to Azure subscriptions.
blog · netspi.com
Running PowerShell on Azure VMs at Scale
Karl Fosaaen shows how Azure Contributor rights enable VM command execution as SYSTEM via Invoke-AzureRmVMRunCommand without opening firewall ports, scaling PowerShell across subscription VMs.
blog · netspi.com
Anonymously Enumerating Azure Services
Karl Fosaaen releases a script for anonymous Azure service enumeration, brute forcing DNS across azurewebsites.net, cloudapp.net, and blob.core.windows.net to map a target's public Azure footprint.
back