apollo-server-core vulnerable to URL-based XSS attack affecting IE11 on default landing page
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 enabled. Old browsers visiting your server may be affected if ANY of these apply:
- You do not pass any landing page plugin to the
pluginsoption ofnew ApolloServer. - You pass
ApolloServerPluginLandingPageLocalDefault()orApolloServerPluginLandingPageProductionDefault()to thepluginsoption ofnew ApolloServer.
Browsers visiting your server are NOT affected if ANY of these apply:
- You pass
ApolloServerPluginLandingPageDisabled()to thepluginsoption ofnew ApolloServer. - You pass
ApolloServerPluginLandingPageGraphQLPlayground()to thepluginsoption ofnew ApolloServer. - You pass a custom plugin implementing the
renderLandingPagehook to thepluginsoption ofnew 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:
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.
For more information
If you have any questions or comments about this advisory:
- Open an issue in the Apollo Server repository
- Email us at security@apollographql.com
Credits
This issue was discovered by Adrian Denkiewicz of Doyensec.
Czego dotyczy
Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.
| Platforma | Paczka | Podatne wersje | Poprawka w wersji |
|---|---|---|---|
| Paczka npm | apollo-server-core | >= 3.0.0, < 3.10.1 | 3.10.1 |
Odnośniki
- Słabość (CWE)
CWE-79- Platforma
- npm
- Paczka
apollo-server-core- Ujawniono
- 18.08.2022
- Aktualizacja
- 11.10.2026 10:22
Źródła i licencje
OSV / GitHub Advisory Database - GHSA-2fvv-qxrq-7jq6 - CC BY 4.0
Historia podatności: apollo-server-core
Wszystkie opisane podatności tej paczki (Paczka npm), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.
- Wszystkich wpisów
- 5
- Pierwsza → ostatnia
- 06.2020 03.2026
- Bez poprawki
- 1
- Wykorzystywana w atakach
- 0
Rozkład istotności
- Średnia 4
- Niska 1
Ujawnienia w latach
- 2020: 1
- 2021: 0
- 2022: 2
- 2023: 1
- 2024: 0
- 2025: 0
- 2026: 1
-
apollo-server-core vulnerable to URL-based XSS attack affecting IE11 on default landing page ten wpis
Dowiedz się, które podatności dotyczą Twojej aplikacji
Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.