graphql-audit

A GraphQL security audit identifies vulnerabilities like schema leaks, SQL injection, and authorization bypass by analyzing introspection and field discovery. It tests batching DoS, subscription misuse, and query complexity while fingerprinting the engine to hunt for known CVEs.

You can discover GraphQL fields and types when introspection is disabled by using field discovery techniques. These methods analyze the endpoint to map out hidden types and structures without relying on standard introspection queries.

Testing GraphQL batching for denial of service involves sending multiple queries in a single request to overload the server. Improper direct object reference checks are performed simultaneously to see if authorization can be bypassed across batched operations.

Yes, GraphQL security audits explicitly check for SQL/NoSQL injection and authorization bypass vulnerabilities. They inject malicious payloads and test access controls to identify instances where authentication or database queries can be improperly manipulated.

Identifying GraphQL engine versions and potential CVEs is best achieved through fingerprinting techniques. By analyzing endpoint responses, you can determine the underlying engine version and cross-reference it with known security vulnerabilities.

Yes, the GraphQL security audit provides WAF bypass techniques. It includes specific methods to circumvent web application firewalls, allowing the audit to successfully execute vulnerability checks for underlying injection and authorization bypass issues.