graphql-tools: GraphQL Tools: Shared legacy executor routes one subscription's results to a different caller
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
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 reuses one WebSocket and replaces its single websocket.onmessage handler whenever a new overlapping subscription starts. The handler delivers LEGACY_WS.DATA frames to the newest observer without comparing data.id with the subscription operation id, so a caller using the same executor can receive another user's authorized subscription payload while the earlier caller's stream is starved. This issue is fixed in version 1.1.36 of the GraphQL Tools legacy WebSocket executor package.
Text from CVE List
Affected versions 2
- graphql-toolsaffected: < 9.0.36CVE List
- executor-legacy-wsaffected: < 1.1.36CVE List
References 4
- github.com/ardatan/graphql-tools/commit/c2f226e6f68236be9e4a577f29faeaa92547458bFixvia CVE List
- github.com/ardatan/graphql-tools/releases/tag/@graphql-tools/executor-legacy-ws@1.1.36Fixvia CVE List
- github.com/ardatan/graphql-tools/security/advisories/GHSA-mp66-8ww2-pcwmAdvisoryvia CVE List
- github.com/ardatan/graphql-tools/pull/8480Referencevia CVE List