Skip to content

Commit 9508f50

Browse files
authored
Update aws-secrets-manager-privesc.md
1 parent e188809 commit 9508f50

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

src/pentesting-cloud/aws-security/aws-privilege-escalation/aws-secrets-manager-privesc.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,10 +18,11 @@ An attacker with this permission can get the **saved value inside a secret** in
1818
aws secretsmanager get-secret-value --secret-id <secret_name> # Get value
1919
```
2020

21-
`secretsmanager:BatchGetSecretValue` needs also `secretsmanager:GetSecretValue` to retrieve the secrets.
22-
2321
**Potential Impact:** Access high sensitive data inside AWS secrets manager service.
2422

23+
> [!WARNING]
24+
> Note that even with the `secretsmanager:BatchGetSecretValue` permission an atatcker would also need `secretsmanager:GetSecretValue` to retrieve the sensitive secrets.
25+
2526
### `secretsmanager:GetResourcePolicy`, `secretsmanager:PutResourcePolicy`, (`secretsmanager:ListSecrets`)
2627

2728
With the previous permissions it's possible to **give access to other principals/accounts (even external)** to access the **secret**. Note that in order to **read secrets encrypted** with a KMS key, the user also needs to have **access over the KMS key** (more info in the [KMS Enum page](../aws-services/aws-kms-enum.md)).

0 commit comments

Comments
 (0)