AWS kms high security documentation change
Summary
Added warning about bypass risk when using kms:RequestAlias in Deny policies and recommended kms:ResourceAliases instead
Security assessment
The change addresses a policy bypass vulnerability where attackers could use alternate identifiers (key ID/ARN/other aliases) to circumvent access controls. This directly impacts authorization security by documenting proper condition key usage.
Diff
diff --git a/kms/latest/developerguide/alias-authorization.md b/kms/latest/developerguide/alias-authorization.md index e47aec5e5..f59bc4842 100644 --- a//kms/latest/developerguide/alias-authorization.md +++ b//kms/latest/developerguide/alias-authorization.md @@ -41,0 +42,4 @@ Allow or deny access to a KMS key based on the alias that identifies the KMS key +###### Important + +A `Deny` policy statement with the `kms:RequestAlias` condition is not recommended because callers can bypass it by using the [key ID](./concepts.html#key-id-key-id), [key ARN](./concepts.html#key-id-key-ARN), or a different alias to identify the KMS key in the request. To deny access based on aliases associated with a KMS key, use the [kms:ResourceAliases](./conditions-kms.html#conditions-kms-resource-aliases) condition key instead. +