v2.4.0: add GraphQL-specific checks (field suggestions + query batching) - #14
Merged
Conversation
New GraphQlCheck (active, PER_HOST, deduped per host+path) adds two GraphQL weaknesses Burp's native scanner does not cover: - Field-suggestion leakage (API9): probes a misspelled meta-field (__typenaem); fires only when the response returns a "Did you mean" hint AND reads as a GraphQL error. Lets an attacker recover the schema even with introspection disabled. Cross-references the native GraphQL introspection / endpoint-found issues. - Array query batching (API4): sends a two-operation JSON array; fires only when the server returns a 2-element result array (both executed). Array batching is not the GraphQL default, so this is a real config signal — an amplification / rate-limit-bypass primitive. Both probes are read-only (__typename), gated by a new HttpUtils.isGraphQlRequest(), reuse the original request's auth headers, and attach the probe as evidence. Endpoint discovery and introspection detection are left to native (no duplication). Docs updated (README, CLAUDE, BURP_DAST_GUIDE, VALIDATION_GUIDE, BAPP_DESCRIPTION): 16 checks / 10 active; GraphQL coverage noted under API4 and API9; also fixed a duplicated Parameter Pollution note in the DAST guide. Version 2.3.2 -> 2.4.0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First additive feature since publication — GraphQL coverage native scanning doesn't provide.
New:
GraphQlCheck(active,PER_HOST)Gated by a new
HttpUtils.isGraphQlRequest(); deduped per(host, path); both probes read-only (__typename), reusing the original request's auth headers and attaching the probe as evidence.__typenaem; fires only when the response carries aDid you mean …hint and reads as a GraphQL error. Lets an attacker recover the schema field-by-field even with introspection off. Deep-links the native GraphQL introspection enabled / endpoint found issues.Deliberately not duplicated: endpoint discovery and introspection detection are native, so we don't re-raise them (introspection is cross-referenced instead). Query-depth/DoS was scoped out (FP-prone + can stress the live target).
Detection discipline
Did you meanpresent) + GraphQL-error shape required → no generic "did you mean" FPs. Low/Firm.Docs
16 checks / 10 active across README, CLAUDE, BURP_DAST_GUIDE, VALIDATION_GUIDE, BAPP_DESCRIPTION; GraphQL noted under API4 + API9. Also fixed a pre-existing duplicated "Parameter Pollution note" in the DAST guide. Version
2.3.2 → 2.4.0.🤖 Generated with Claude Code