Apollo Server is vulnerable to denial of service with `startStandaloneServer`
apollographql apollo-server
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| apollo-server npm |
| No fix yet |
| @apollo/server npm |
|
|
apollographql apollo-server
| Product | Affected | Fixed in |
|---|---|---|
| apollo-server npm |
| No fix yet |
| @apollo/server npm |
|
|
Apollo Server is an open-source, spec-compliant GraphQL server that's compatible with any GraphQL client, including Apollo Client. In versions from 2.0.0 to 3.13.0, 4.2.0 to before 4.13.0, and 5.0.0 to before 5.4.0, the default configuration of startStandaloneServer from @apollo/server/standalone is vulnerable to denial of service (DoS) attacks through specially crafted request bodies with exotic character set encodings. This issue does not affect users that use @apollo/server as a dependency for integration packages, like @as-integrations/express5 or @as-integrations/next, only direct usage of startStandaloneServer.
From the CVE record · GitHub_M
The default configuration of startStandaloneServer in affected Apollo Server versions is vulnerable to denial of service through specially crafted request bodies with exotic character set encodings. An attacker can trigger this by sending requests; the input does not specify whether authentication is required. Usage through integration packages is not affected.
Check direct users of startStandaloneServer running npm apollo-server 2.0.0–3.13.0 or @apollo/server 4.2.0–before 4.13.0 or 5.0.0–before 5.4.0.