GraphQL resolver or field authorization failure
A GraphQL path or protected field bypasses the permission enforced for the same object elsewhere.
Candidate CWE: CWE-863
Test hypothesis#
Use an observed query on controlled O1. Replay as B, request one protected field, and compare an observed node/nested route. Keep aliases to two items and avoid recursive complexity tests.
Evidence required#
The response contains forbidden controlled data or a committed mutation, even if another field returns an error. Include operation, variables, role, and relevant partial data.
Rule out false positives#
Introspection, public schema fields, HTTP 200 with only errors, or an intentionally accessible object is not an authorization finding.
Playbook and command references#
- REST, GraphQL, gRPC, WebSocket, and SSE permission parity — Carry the same permission invariant across protocols, nested fields, streams, and alternate API versions.
- Object, function, and property authorization — Turn identities, tenants, objects, roles, and lifecycle transitions into a reproducible permission matrix.
Find the associated command snippets
Referenced by these target playbooks#
Report checklist#
- Capture the affected version, configuration, identities, and object ownership.
- Preserve a valid baseline and a negative control.
- Reproduce the forbidden data access, action, or state change on controlled fixtures.
- Explain the intended security rule and why the observed behavior violates it.
- State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.
Conditional ATT&CK mapping#
No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.