AWS appsync: Move x-forwarded-for spoofing warning next to sourceIp
Summary
The Important note warning that clients and proxies can set the `x-forwarded-for` header and that only the last element of `sourceIp` should be used for authorization decisions was relocated to directly follow the `sourceIp` field description.
Security assessment
The warning documents a real spoofing risk (unverified x-forwarded-for values feeding sourceIp) and advises using only the last element for authorization decisions; the change is a relocation of existing guidance, so it is security documentation rather than a fix for a specific reported vulnerability.
Evidence
+Clients and intermediate proxies can set the `x-forwarded-for` header to any value, and AWS AppSync doesn't verify it. Use only the last element of `sourceIp` for authorization decisions, and sanitize the other entries before you use them.
Diff
diff --git a/appsync/latest/devguide/resolver-context-reference-js.md b/appsync/latest/devguide/resolver-context-reference-js.md index 2edc287..30e33ca 100644 --- a//appsync/latest/devguide/resolver-context-reference-js.md +++ b//appsync/latest/devguide/resolver-context-reference-js.md @@ -243,0 +244,4 @@ A list of the source IP addresses for the request that AWS AppSync receives. If +###### Important + +Clients and intermediate proxies can set the `x-forwarded-for` header to any value, and AWS AppSync doesn't verify it. Use only the last element of `sourceIp` for authorization decisions, and sanitize the other entries before you use them. + @@ -264,4 +267,0 @@ The user name of the authenticated user. In the case of `AMAZON_COGNITO_USER_POO -###### Important - -Clients and intermediate proxies can set the `x-forwarded-for` header to any value, and AWS AppSync doesn't verify it. Use only the last element of `sourceIp` for authorization decisions, and sanitize the other entries before you use them. -