GraphQL Tools: Per-request connection parameters persist into later users' WebSocket authentications

Summary

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.

Remediation

1. Inventory every ardatan graphql-tools deployment, including staging.
2. No fixed version appears in the public sources yet. Check the references below and the vendor directly.

References

• Referencehttps://github.com/ardatan/graphql-tools/commit/c2f226e6f68236be9e4a577f29faeaa92547458b
• Referencehttps://github.com/ardatan/graphql-tools/pull/8480
• Referencehttps://github.com/ardatan/graphql-tools/releases/tag/@graphql-tools/[email protected]
• Referencehttps://github.com/ardatan/graphql-tools/security/advisories/GHSA-434m-5hcj-pxf3