Skip to content

Commit 816da7a

Browse files
committed
fix
1 parent 041a508 commit 816da7a

File tree

3 files changed

+2
-2
lines changed

3 files changed

+2
-2
lines changed

src/images/arte.png

2.41 MB
Loading

src/pentesting-cloud/aws-security/aws-services/aws-cognito-enum/cognito-identity-pools.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ For more information check https://github.com/padok-team/cognito-scanner
8888
The only thing an attacker need to know to **get AWS credentials** in a Cognito app as unauthenticated user is the **Identity Pool ID**, and this **ID must be hardcoded** in the web/mobile **application** for it to use it. An ID looks like this: `eu-west-1:098e5341-8364-038d-16de-1865e435da3b` (it's not bruteforceable).
8989

9090
> [!TIP]
91-
> The **IAM Cognito unathenticated role created via is called** by default `Cognito_<Identity Pool name>Unauth_Role`
91+
> The **IAM Cognito unauthenticated role created via is called** by default `Cognito_<Identity Pool name>Unauth_Role`
9292
9393
If you find an Identity Pools ID hardcoded and it allows unauthenticated users, you can get AWS credentials with:
9494

src/pentesting-cloud/azure-security/az-services/vms/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -837,7 +837,7 @@ Invoke-AzureRmVMBulkCMD -Script Mimikatz.ps1 -Verbose -output Output.txt
837837
## Unauthenticated Access
838838
839839
{{#ref}}
840-
../../az-unauthenticated-enum-and-initial-entry/az-vms-unath.md
840+
../../az-unauthenticated-enum-and-initial-entry/az-vms-unauth.md
841841
{{#endref}}
842842
843843
## Post Exploitation

0 commit comments

Comments
 (0)