Skip to content
StrikeOps

GraphQL Introspection Enabled in Production

LowTypical severity Web applications and APIsCWE-200

01Description

The production GraphQL endpoint answered introspection queries, returning the full schema including all types, queries and mutations.

02Impact

The full schema gives an attacker a complete map of the API, including administrative and deprecated operations, making it far easier to find authorization flaws.

03Severity

Typically

Low

Typically Low. Low on its own. Raise it if the schema exposes sensitive operations or fields that turn out to lack authorization.

04How to verify

  1. 1Send an introspection query to the GraphQL endpoint.
  2. 2Review the schema for sensitive types, administrative mutations and unused operations.
  3. 3Test discovered operations for authorization flaws.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Disable introspection in production or restrict it to authenticated internal users.
  2. 2Enforce authorization on every resolver regardless.
  3. 3Apply query depth and complexity limits.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo