GraphQL Tools: TLS Certificate Validation Disabled in Legacy GraphQL WebSocket Executor
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.4epss 0.3%
exploitation probability
0.3%top 83% of all CVEs
observed exploitation
nono source reports it
GraphQL Tools provides utilities for building, stitching, and mocking GraphQL schemas. Prior to 1.1.35, the executor-legacy-ws buildWSLegacyExecutor() function hardcodes TLS certificate rejection off for Node.js connections to wss:// endpoints. Applications using the executor directly, or url-loader with SubscriptionProtocol.LEGACY_WS, can therefore accept an attacker-controlled certificate when a network-positioned attacker intercepts the connection. Authentication material in connectionParams or headers can be disclosed, and subscription data can be modified. Browser WebSocket clients are unaffected because browsers enforce certificate validation. This issue is fixed in version 1.1.35.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
References
https://github.com/ardatan/graphql-tools/commit/3831a0661514c91d99971052f983552556880402https://github.com/ardatan/graphql-tools/pull/8426https://github.com/ardatan/graphql-tools/releases/tag/@graphql-tools/executor-legacy-ws@1.1.35https://github.com/ardatan/graphql-tools/security/advisories/GHSA-6fw5-9hq8-w87g