GHSA-733v-p3h5-qpq7: @escape.tech/graphql armor cost limit GraphQL Armor Cost-Limit Plugin Bypass Vulnerability
MODERATEGHSA-733v-p3h5-qpq7 is a MODERATE (CVSS 5.3) graphql armor cost-limit plugin bypass vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting @escape.tech/graphql armor cost limit libraries in the npm ecosystem. The issue involves graphql armor cost-limit plugin bypass via introspection query obfuscation. Remediation is available by upgrading affected packages to version 2.4.2.
GHSA-733v-p3h5-qpq7 at a Glance
Security Impact
CVSS: 5.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).
How to Fix GHSA-733v-p3h5-qpq7
To remediate this vulnerability, upgrade all affected @escape.tech/graphql armor cost limit dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @escape.tech/graphql-armor-cost-limit@2.4.2Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @escape.tech/graphql-armor-cost-limitHow to Check if You Are Affected
To determine whether your Node.js application is affected by GHSA-733v-p3h5-qpq7, inspect your project dependencies using npm:
npm ls @escape.tech/graphql-armor-cost-limitAnalyze the terminal output to locate any version of @escape.tech/graphql armor cost limit in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.4.2), your application is affected.
Note: The npm ls @escape.tech/graphql-armor-cost-limit command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In @escape.tech/graphql armor cost limit, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-733v-p3h5-qpq7 Affected @escape.tech/graphql armor cost limit Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@escape.tech/graphql-armor-cost-limit
|
npm |
< 2.4.2
|
2.4.2
|
References
Frequently Asked Questions
What is GHSA-733v-p3h5-qpq7?
Which @escape.tech/graphql armor cost limit versions are affected?
What version fixes GHSA-733v-p3h5-qpq7?
Is @escape.tech/graphql-armor-cost-limit affected?
What is the CVSS score of GHSA-733v-p3h5-qpq7?
What CWE is associated with GHSA-733v-p3h5-qpq7?
How can I check npm dependencies for GHSA-733v-p3h5-qpq7?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-733v-p3h5-qpq7",
"modified" : "2025-04-29T16:45:56Z",
"published" : "2025-04-25T15:14:36Z",
"aliases" : [ ],
"summary" : "GraphQL Armor Cost-Limit Plugin Bypass via Introspection Query Obfuscation",
"details" : "### Summary\nA query cost restriction using the `cost-limit` can be bypassed if `ignoreIntrospection` is enabled (which is the default configuration) by naming your query/fragment `__schema`.\n\n### Details\nAt the start of the `computeComplexity` function, we have the following check for `ignoreIntrospection` option:\n\n```ts\n if (this.config.ignoreIntrospection && 'name' in node && node.name?.value === '__schema') {\n return 0;\n }\n```\n\nHowever, the `node` can be `FieldNode | FragmentDefinitionNode | InlineFragmentNode | OperationDefinitionNode | FragmentSpreadNode`\n\nSo, for example, sending the following query\n\n```gql\nquery hello {\n books {\n title\n }\n}\n```\n\nwould create an `OperationDefinitionNode` with `node.name.value == 'hello'`\n\nThe proper way to handle this would be to check for the `__schema` field, which would create a `FieldNode`.\n\nThe fix is\n\n```ts\n if (\n this.config.ignoreIntrospection &&\n 'name' in node &&\n node.name?.value === '__schema' &&\n node.kind === Kind.FIELD\n ) {\n return 0;\n }\n```\n\nto assert that the node must be a `FieldNode`\n\n### PoC\n```gql\nquery {\n ...__schema\n}\n\nfragment __schema on Query {\n books {\n title\n author\n }\n}\n```\n\n```gql\nquery __schema {\n books {\n title\n author\n }\n}\n```\n\n### Impact\nApplications using GraphQL Armor Cost Limit plugin with `ignoreIntrospection` enabled.\n\n### Fix:\nFixed on [772](https://github.com/Escape-Technologies/graphql-armor/pull/772). A quick patch would be to set `ignoreIntrospection` to false.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@escape.tech/graphql-armor-cost-limit"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.4.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/Escape-Technologies/graphql-armor/security/advisories/GHSA-733v-p3h5-qpq7"
}, {
"type" : "WEB",
"url" : "https://github.com/Escape-Technologies/graphql-armor/pull/772"
}, {
"type" : "WEB",
"url" : "https://github.com/Escape-Technologies/graphql-armor/commit/5a329541cf32a359ee1f69748738f91231b26eba"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/Escape-Technologies/graphql-armor"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-400", "CWE-770" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2025-04-25T15:14:36Z",
"nvd_published_at" : null
}
}