AWS iot: Document wildcard limitation for certificate policy variables
Summary
Adds a note that AWS IoT Core does not substitute a certificate policy variable when the certificate attribute value contains a wildcard character (*, $, +, ?, #), leaving ${policy-variable} unsubstituted, with a link to policy variable limitations.
Security assessment
Documents that wildcard characters in certificate attributes are not substituted into policy variables, preventing wildcard injection into IoT policy resource/condition values. This is security-relevant authorization behavior documentation, not a specific CVE fix.
Evidence
AWS IoT Core also doesn't replace a certificate policy variable when the certificate attribute value contains a wildcard character (`*`, `$`, `+`, `?`, or `#`). In that case, the `${policy-variable}` remains unsubstituted.
Diff
diff --git a/iot/latest/developerguide/cert-policy-variables.md b/iot/latest/developerguide/cert-policy-variables.md index 4affb8f..7651a35 100644 --- a//iot/latest/developerguide/cert-policy-variables.md +++ b//iot/latest/developerguide/cert-policy-variables.md @@ -16,0 +17,2 @@ If your X.509 certificate doesn't include a particular certificate attribute but +AWS IoT Core also doesn't replace a certificate policy variable when the certificate attribute value contains a wildcard character (`*`, `$`, `+`, `?`, or `#`). In that case, the `${policy-variable}` remains unsubstituted. For this and other limitations that apply to certificate policy variables, see [X.509 Certificate policy variable limitations](./use-policy-variables.html#policy-limits). +