InQL v6.1.0 Just Landed with New Features and Contribution S... #1630
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.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
This post announces InQL v6.1.0, a Burp Suite extension focused on offensive GraphQL security testing. The extension was fully rewritten from Jython to Kotlin in v6.0.0 and v6.1.0 adds several key features that help discover and exploit attack surface on GraphQL APIs even when introspection is disabled.
GraphQL schema brute-forcer (active schema reconstruction).
Earlier versions of InQL relied on GraphQL introspection or a local schema file. v6.1.0 intro...
🔧 Technical Details
GraphQL schema reconstruction via error-based brute forcing.
The post details a technique to reconstruct GraphQL schemas when introspection is disabled by sending batched queries with guessed field/argument names and parsing validation errors. By iterating over a wordlist, the attacker observes responses like
Field 'X' not found on type 'Y',Argument 'Z' is required, or suggestion hints such asDid you mean 'openPR'?. These messages reveal valid types, fields, required arguments, and even type names. Additional requests with deliberately incorrect value types provoke type mismatch errors that expose whether an argument expectsString, a custom object, or a list type (e.g.,[Episode!]). Repeating this process allows an attacker to reconstruct much of the schema purely from server feedback, enabling targeted abuse of sensitive queries and mutations.GraphQL engine fingerprinting from er...
🤖 Agent Actions
Summary:
Tests: Not run (not requested).
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.