GHSA-hmfr-rx46-4jx2 – @escape.tech/graphql-armor-max-depth

Package

Manager: npm
Name: @escape.tech/graphql-armor-max-depth
Vulnerable Version: >=0 <2.4.2

Severity

Level: Medium

CVSS v3.1: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

EPSS: N/A pctlN/A

Details

GraphQL Armor Max-Depth Plugin Bypass via Introspection Query Obfuscation ### Summary A query depth restriction using the `max-depth` property can be bypassed if `ignoreIntrospection` is enabled (which is the default configuration) by naming your query/fragment `__schema`. ### Details At the start of the `countDepth` function, we have the following check for the `ignoreIntrospection` option: ```typescript if (this.config.ignoreIntrospection && 'name' in node && node.name?.value === '__schema') { return 0; } ``` However, the `node` can be one of: `FieldNode`, `FragmentDefinitionNode`, `InlineFragmentNode`, `OperationDefinitionNode`, `FragmentSpreadNode`. For example, consider sending the following query: ```graphql query hello { books { title } } ``` This would create an `OperationDefinitionNode` where `node.name.value == 'hello'` The proper way to handle this is to check explicitly for the `__schema` field, which corresponds to a `FieldNode`. The fix is ```typescript if ( this.config.ignoreIntrospection && 'name' in node && node.name?.value === '__schema' && node.kind === Kind.FIELD ) { return 0; } ``` This ensures that the node is explicitly a `FieldNode`. ### PoC Max depth: `6` ```graphql query { books { author { books { author { ...__schema } } } } } fragment __schema on Author { books { title } } ``` ### Impact This issue affects applications using the GraphQL Armor Depth Limit plugin with `ignoreIntrospection` enabled. ### Fix This is fixed in [PR#823](https://github.com/Escape-Technologies/graphql-armor/pull/823)

Metadata

Created: 2025-08-26T18:42:37Z
Modified: 2025-08-26T18:42:37Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/08/GHSA-hmfr-rx46-4jx2/GHSA-hmfr-rx46-4jx2.json
CWE IDs: ["CWE-400"]
Alternative ID: N/A
Finding: F002
Auto approve: 1