Document live-validated AWS data-access techniques - #379
Merged
Conversation
Collaborator
Author
|
Added a second tested batch in
Every section includes a no-list fallback, exact tested impact, external-account negative control, and cleanup result. The earlier principal/account validation techniques remain explicitly classified as expected post-exploitation reconnaissance, not vulnerabilities or zero-days. |
Collaborator
Author
|
Added another live-validated service page in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents only techniques reproduced in disposable AWS scenarios with exact constrained permissions. Content follows the existing per-service hierarchy and includes commands, prerequisites, no-list discovery fallbacks, limitations, and cleanup evidence.
Validated techniques include AppStream home-folder access through CreateStreamingURL; AppSync API-key theft with real GraphQL data retrieval; AppConfig, Batch, CloudFormation, Glue, Image Builder, Managed Flink, EMR Serverless, EventBridge Pipes/rules/Scheduler, SageMaker, SSM, Step Functions, Auto Scaling, and Elastic Beanstalk configuration disclosures.
Elastic Beanstalk is documented only as the exact tested multi-permission combination; its describe action alone was insufficient. WorkMail and unvalidated EUC candidates are not promoted.
Validation