Security Test: Width limit¶

Scanner(s) Support¶

Description¶

Default Severity: low

Without limits on how many nested subfields a GraphQL query can request, an attacker might craft an overly large query that strains your system by requesting far more data than intended. This vulnerability is dangerous because it can lead to performance issues, such as slowing down or even crashing the server, and it might expose more information than expected. Developers often overlook setting restrictions on query depth or width, which leaves applications open to denial-of-service attacks and unintentional data leakage if not properly managed.

Reference:

• https://www.apollographql.com/blog/graphql/security/securing-your-graphql-api-from-malicious-queries/

Configuration¶

Identifier: resource_limitation/graphql_width_limit

Examples¶

All configuration available:

checks:
  resource_limitation/graphql_width_limit:
    skip: false # default
    options:
      threshold: 20 # default

Options¶

Options can be set in the options key of the Security Test Configuration.

Compliance and Standards¶