Ardatan graphql-tools
GraphQL Tools: Per-request connection parameters persist into later users' WebSocket authentications
GraphQL Tools provides utilities for building, stitching, and mocking GraphQL schemas. Prior to version 1.1.36 of the GraphQL Tools legacy WebSocket executor package, buildWSLegacyExecutor in packages/executors/legacy-ws/src/index.ts retains request.extensions.connectionParams in the closure-scoped executorConnectionParams object after cleanupWebsocket closes a connection. When one executor is reused across different authorization contexts, a later request that omits a sensitive key can send an earlier caller's Authorization or tenant value in its connection_init payload, causing the downstream server to authenticate the later caller as the earlier user. Applications that create a new executor for every request are not affected. This issue is fixed in version 1.1.36 of the GraphQL Tools legacy WebSocket executor package.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 9.0.36
Fixed in 9.0.36
- < 1.1.36
Fixed in 1.1.36
Mitigation
Upgrade graphql-tools to 9.0.36 or later.
Upgrade executor-legacy-ws to 1.1.36 or later.
References
- Vendor advisory github.com/ardatan/graphql-tools/security/advi…
- Patch github.com/ardatan/graphql-tools/pull/8480
- Patch github.com/ardatan/graphql-tools/commit/c2f226…
1 more
- Release notes github.com/ardatan/graphql-tools/releases/tag/…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.