-
Notifications
You must be signed in to change notification settings - Fork 220
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
New attack technique: SES enumeration activities (#501)
* New attack technique: ses enumeration activities Co-authored-by: Alessandro Brucato <alessandro.brucato@protonmail.com> Signed-off-by: Lorenzo Susini <susinilorenzo1@gmail.com> * Add missing dependency * Cosmetic code enhancements * Don't use an additional IAM role, and enumerate additional things * Only use SES (not SESv2) API calls following recommendation from an IR practitioner * Generate docs --------- Signed-off-by: Lorenzo Susini <susinilorenzo1@gmail.com> Co-authored-by: Alessandro Brucato <alessandro.brucato@protonmail.com> Co-authored-by: Christophe Tafani-Dereeper <christophe.tafanidereeper@datadoghq.com>
- Loading branch information
3 people
authored
Apr 8, 2024
1 parent
f84ad92
commit 6e97276
Showing
8 changed files
with
175 additions
and
13 deletions.
There are no files selected for viewing
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,51 @@ | ||
| --- | ||
| title: Enumerate SES | ||
| --- | ||
|
|
||
| # Enumerate SES | ||
|
|
||
|
|
||
| <span class="smallcaps w3-badge w3-blue w3-round w3-text-white" title="This attack technique can be detonated multiple times">idempotent</span> | ||
|
|
||
| Platform: AWS | ||
|
|
||
| ## MITRE ATT&CK Tactics | ||
|
|
||
|
|
||
| - Discovery | ||
|
|
||
| ## Description | ||
|
|
||
|
|
||
| Simulates an attacker enumerating SES. Attackers frequently use this enumeration technique after having compromised an access key, to use it to launch phishing campaigns or further resell stolen credentials. | ||
|
|
||
| <span style="font-variant: small-caps;">Warm-up</span>: None. | ||
|
|
||
| <span style="font-variant: small-caps;">Detonation</span>: | ||
|
|
||
| - Perform <code>ses:GetAccountSendingEnabled</code> to check if SES sending is enabled. | ||
| - Perform <code>ses:GetSendQuota</code> to discover the current [email sending quotas](https://docs.aws.amazon.com/ses/latest/APIReference/API_GetSendQuota.html). | ||
| - Perform <code>ses:ListIdentities</code> to discover the list of [identities](https://docs.aws.amazon.com/ses/latest/APIReference/API_ListIdentities.html) in the account. | ||
| - If identities are found, use <code>ses:GetIdentityVerificationAttributes</code> (only once) to discover [verification status](https://docs.aws.amazon.com/ses/latest/APIReference/API_GetIdentityVerificationAttributes.html) of each identity. | ||
|
|
||
| References: | ||
|
|
||
| - https://securitylabs.datadoghq.com/articles/following-attackers-trail-in-aws-methodology-findings-in-the-wild/#most-common-enumeration-techniques | ||
| - https://www.invictus-ir.com/news/ransomware-in-the-cloud | ||
| - https://unit42.paloaltonetworks.com/compromised-cloud-compute-credentials/#post-125981-_kdq0vw6banab | ||
| - https://permiso.io/blog/s/aws-ses-pionage-detecting-ses-abuse/ | ||
| - https://www.invictus-ir.com/news/the-curious-case-of-dangerdev-protonmail-me | ||
|
|
||
|
|
||
| ## Instructions | ||
|
|
||
| ```bash title="Detonate with Stratus Red Team" | ||
| stratus detonate aws.discovery.ses-enumerate | ||
| ``` | ||
| ## Detection | ||
|
|
||
|
|
||
| Through CloudTrail's <code>GetAccountSendingEnabled</code>, <code>GetSendQuota</code> and <code>ListIdentities</code> events. | ||
| These can be considered suspicious especially when performed by a long-lived access key, or when the calls span across multiple regions. | ||
|
|
||
|
|
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
94 changes: 94 additions & 0 deletions
94
v2/internal/attacktechniques/aws/discovery/ses-enumerate/main.go
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,94 @@ | ||
| package aws | ||
|
|
||
| import ( | ||
| "context" | ||
| _ "embed" | ||
| "fmt" | ||
| "github.com/datadog/stratus-red-team/v2/pkg/stratus" | ||
| "github.com/datadog/stratus-red-team/v2/pkg/stratus/mitreattack" | ||
| "log" | ||
|
|
||
| "github.com/aws/aws-sdk-go-v2/service/ses" | ||
| ) | ||
|
|
||
| func init() { | ||
| stratus.GetRegistry().RegisterAttackTechnique(&stratus.AttackTechnique{ | ||
| ID: "aws.discovery.ses-enumerate", | ||
| FriendlyName: "Enumerate SES", | ||
| Description: ` | ||
| Simulates an attacker enumerating SES. Attackers frequently use this enumeration technique after having compromised an access key, to use it to launch phishing campaigns or further resell stolen credentials. | ||
| Warm-up: None. | ||
| Detonation: | ||
| - Perform <code>ses:GetAccountSendingEnabled</code> to check if SES sending is enabled. | ||
| - Perform <code>ses:GetSendQuota</code> to discover the current [email sending quotas](https://docs.aws.amazon.com/ses/latest/APIReference/API_GetSendQuota.html). | ||
| - Perform <code>ses:ListIdentities</code> to discover the list of [identities](https://docs.aws.amazon.com/ses/latest/APIReference/API_ListIdentities.html) in the account. | ||
| - If identities are found, use <code>ses:GetIdentityVerificationAttributes</code> (only once) to discover [verification status](https://docs.aws.amazon.com/ses/latest/APIReference/API_GetIdentityVerificationAttributes.html) of each identity. | ||
| References: | ||
| - https://securitylabs.datadoghq.com/articles/following-attackers-trail-in-aws-methodology-findings-in-the-wild/#most-common-enumeration-techniques | ||
| - https://www.invictus-ir.com/news/ransomware-in-the-cloud | ||
| - https://unit42.paloaltonetworks.com/compromised-cloud-compute-credentials/#post-125981-_kdq0vw6banab | ||
| - https://permiso.io/blog/s/aws-ses-pionage-detecting-ses-abuse/ | ||
| - https://www.invictus-ir.com/news/the-curious-case-of-dangerdev-protonmail-me | ||
| `, | ||
| Detection: ` | ||
| Through CloudTrail's <code>GetAccountSendingEnabled</code>, <code>GetSendQuota</code> and <code>ListIdentities</code> events. | ||
| These can be considered suspicious especially when performed by a long-lived access key, or when the calls span across multiple regions. | ||
| `, | ||
| Platform: stratus.AWS, | ||
| IsIdempotent: true, | ||
| MitreAttackTactics: []mitreattack.Tactic{mitreattack.Discovery}, | ||
| Detonate: detonate, | ||
| }) | ||
| } | ||
|
|
||
| func detonate(_ map[string]string, providers stratus.CloudProviders) error { | ||
| awsConnection := providers.AWS().GetConnection() | ||
| sesClient := ses.NewFromConfig(awsConnection) | ||
|
|
||
| log.Println("Checking is SES e-mail sending is enabled in the current region") | ||
| result, err := sesClient.GetAccountSendingEnabled(context.Background(), &ses.GetAccountSendingEnabledInput{}) | ||
| if err != nil { | ||
| return fmt.Errorf("unable to check if SES sending is enabled: %w", err) | ||
| } | ||
| if result.Enabled { | ||
| log.Println("SES e-mail sending is enabled") | ||
| } else { | ||
| log.Println("SES e-mail sending is disabled") | ||
| } | ||
|
|
||
| log.Println("Enumerating verified SES identities using ses:ListIdentities") | ||
| identities, err := sesClient.ListIdentities(context.Background(), &ses.ListIdentitiesInput{}) | ||
| if err != nil { | ||
| return fmt.Errorf("unable to list SES identities: %w", err) | ||
| } | ||
|
|
||
| if len(identities.Identities) == 0 { | ||
| log.Println("No verified SES identities found") | ||
| } else { | ||
| log.Printf("Found %d verified SES identities", len(identities.Identities)) | ||
| verificationAttributes, err := sesClient.GetIdentityVerificationAttributes(context.Background(), &ses.GetIdentityVerificationAttributesInput{ | ||
| Identities: identities.Identities, | ||
| }) | ||
| if err != nil { | ||
| return fmt.Errorf("unable to get identity verification attributes: %w", err) | ||
| } | ||
| for identity := range verificationAttributes.VerificationAttributes { | ||
| log.Printf("- Identity %s has verification status '%s'", identity, verificationAttributes.VerificationAttributes[identity].VerificationStatus) | ||
| } | ||
| } | ||
|
|
||
| log.Println("Enumerating SES quotas") | ||
| quotas, err := sesClient.GetSendQuota(context.Background(), &ses.GetSendQuotaInput{}) | ||
| if err != nil { | ||
| return fmt.Errorf("unable to get SES quotas: %w", err) | ||
| } | ||
|
|
||
| log.Printf("Current quotas: max24hoursend: %d, maxsendrate: %d, sentlast24hours: %d\n", int(quotas.Max24HourSend), int(quotas.MaxSendRate), int(quotas.SentLast24Hours)) | ||
|
|
||
| return nil | ||
| } |
This file contains 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