AWS appsync: Move x-forwarded-for spoofing warning next to sourceIp
Summary
In the AppSync resolver context reference, the Important note about unverified `x-forwarded-for` values and using only the last element of `sourceIp` for authorization decisions was moved to immediately follow the `sourceIp` field description.
Security assessment
Same security guidance as the JS resolver page, repositioned for visibility; it warns about header spoofing affecting IP-based authorization but does not itself remediate a specific 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.md b/appsync/latest/devguide/resolver-context-reference.md index c71fdd3..090adbd 100644 --- a//appsync/latest/devguide/resolver-context-reference.md +++ b//appsync/latest/devguide/resolver-context-reference.md @@ -216,0 +217,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. + @@ -237,4 +240,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. -