-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configuration for disabling aliases #1093
Comments
GraphQL Java has some configurable limits related to DoS. It would make sense for checks like these to be performed at that level too as they require understanding and parsing the query. Please, consider asking in https://github.com/graphql-java/graphql-java. |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
Hi team,
As per this article, alias overloading could be used for DoS attacks. There are a few options for preventing these attacks like limiting the request body, limiting the number of aliases and disabling them. I couldn't find any configuration for disabling aliases and I had to implement a filter in my application.
Do you plan to provide some kind of configuration for disabling aliases( for example, application property ), so that people could use it out of the box, as it is a general problem?
I paste the solution with filter for a reference:
where
CachedBodyHttpServletRequest
is just a wrapper for the request.Best regards,
Denis.
The text was updated successfully, but these errors were encountered: