Skip to content

Mwaa post exploitation #226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 5 commits into from
Oct 23, 2025
Merged

Mwaa post exploitation #226

merged 5 commits into from
Oct 23, 2025

Conversation

@AI-redteam
Copy link
Contributor

@AI-redteam AI-redteam commented Oct 23, 2025

AWS MWAA Execution Role Vulnerability:

    • MWAA requires wildcard account ID in SQS permissions (arn:aws:sqs::airflow-celery-) - cannot be fixed without breaking the service
  • -Allows any DAG to send data to external SQS queues in any AWS account
    • Enables data exfiltration, C2 channels, and cross-account attacks
    • Bypasses all network controls - works even in private VPCs via AWS internal APIs
    • Architectural flaw in AWS's official documentation with no mitigation available

@AI-redteam
Add AWS MWAA post-exploitation documentation
6fc8a81 
Document the security risks and attack vectors associated with AWS MWAA's execution role, including data exfiltration and command and control channels.
@AI-redteam
Add README for AWS MWAA post-exploitation
0d4fb44 
fix location and structure
@AI-redteam
Update README to clarify policy tightening process
65a1490 
Clarified the process of tightening the policy after deployment and the implications for defenders.
@AI-redteam
Revise README for AWS MWAA execution role vulnerability
8c472fb 
Updated README to reflect the AWS MWAA execution role vulnerability and its implications for security, including detailed attack vectors
@AI-redteam
Update README to specify Airflow DAG permissions
3f8aa12 
Clarified that all Airflow DAGs run with the execution role's permissions.
@carlospolop carlospolop merged commit a41bcbc into HackTricks-wiki:master Oct 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@AI-redteam @carlospolop