GraphQL Tools: Per-request connection parameters persist into later users' WebSocket authentications
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 9.0.36, 1.1.36
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The GraphQL Tools legacy WebSocket executor package (buildWSLegacyExecutor) is affected when a single executor instance is reused across different users or authorization contexts. In that setup, one caller's authentication or tenant credentials can be sent to the downstream server on a later caller's request, causing that later caller to be authenticated as the earlier user. Applications that create a new executor for each request are not affected.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- ardatan graphql-tools
fixed in 9.0.36
- @graphql-tools executor-legacy-ws
fixed in 1.1.36
- @graphql-tools/executor-legacy-wsnpm
fixed in 1.1.36