Read the docs
TI-2022-26622 Aliases GHSA-2fvv-qxrq-7jq6

apollo-server-core vulnerable to URL-based XSS attack affecting IE11 on default landing page

Priority LOW 38CWE-79Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
Cross-site scripting
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-79.

Summary

### Impact The default landing page contained HTML to display a sample `curl` command which is made visible if the full landing page bundle could not be fetched from Apollo's CDN. The server's URL is directly interpolated into this command inside the browser from `window.location.href`. On some older browsers such as IE11, this value is not URI-encoded. On such browsers, opening a malicious URL pointing at an Apollo Router could cause execution of attacker-controlled JavaScript. This only affects Apollo Server with the [default landing page](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/) enabled. Old browsers visiting your server may be affected if ANY of these apply: - You do not pass any landing page plugin to the `plugins` option of `new ApolloServer`. - You pass `ApolloServerPluginLandingPageLocalDefault()` or `ApolloServerPluginLandingPageProductionDefault()` to the `plugins` option of `new ApolloServer`. Browsers visiting your server are NOT affected if ANY of these apply: - You pass `ApolloServerPluginLandingPageDisabled()` to the `plugins` option of `new ApolloServer`. - You pass `ApolloServerPluginLandingPageGraphQLPlayground()` to the `plugins` option of `new ApolloServer`. - You pass a custom plugin implementing the `renderLandingPage` hook to the `plugins` option of `new ApolloServer`. This issue was introduced in v3.0.0 when the landing page feature was added. ### Patches To avoid this, the sample `curl` command has been removed in release 3.10.1. ### Workarounds Disabling the landing page removes the possibility of exploit: ```ts import { ApolloServerPluginLandingPageDisabled } from 'apollo-server-core'; new ApolloServer({ plugins: [ApolloServerPluginLandingPageDisabled()], // ... }); ``` ### See also A similar issue exists in the landing page of Apollo Router. See the corresponding [Apollo Router security advisory](https://github.com/apollographql/router/security/advisories/GHSA-p5q6-hhww-f999). ### For more information If you have any questions or comments about this advisory: * Open an issue in [the Apollo Server repository](https://github.com/apollographql/apollo-server/) * Email us at [[email protected]](mailto:[email protected]) ### Credits This issue was discovered by Adrian Denkiewicz of [Doyensec](https://doyensec.com/research.html).

Why it matters now

Fix Fixed apollo-server-core (npm): 3.10.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—apollo-server-core (npm)3.0.0 to before 3.10.13.10.1Patch availableGHSA-2fvv-qxrq-7jq6
  • apollo-server-core (npm) Vendor— Affected 3.0.0 to before 3.10.1 Fixed in 3.10.1 Patch available GHSA-2fvv-qxrq-7jq6

Remediation

  • Fix · GHSA-2fvv-qxrq-7jq6 apollo-server-core (npm) Fixed in 3.10.1 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-2fvv-qxrq-7jq6

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences