You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most GraphQL implementations allow field introspection by default or even consider it as part of the spec. Without this feature, clients relying on introspection (like GraphiQL) won't work.
As discussed in the OWASP guide, some consider that introspection allows attacker to learn about queries and data types. In this case, GraphQL clients should be given the schema out-of-band and rely on a different source of information to learn about the API.
The same guide argues that disabling introspection won't prevent attackers to learn about the API, since brute-forcing and GraphQL error hints will give the information away quite easily anyway.
Spring Boot should provide an option to disable introspection, but not enable it by default.
The text was updated successfully, but these errors were encountered:
Most GraphQL implementations allow field introspection by default or even consider it as part of the spec. Without this feature, clients relying on introspection (like GraphiQL) won't work.
As discussed in the OWASP guide, some consider that introspection allows attacker to learn about queries and data types. In this case, GraphQL clients should be given the schema out-of-band and rely on a different source of information to learn about the API.
The same guide argues that disabling introspection won't prevent attackers to learn about the API, since brute-forcing and GraphQL error hints will give the information away quite easily anyway.
Spring Boot should provide an option to disable introspection, but not enable it by default.
The text was updated successfully, but these errors were encountered: