CVE-2025-59052
CVE-2025-59052 · Angular SSR: Global Platform Injector Race Condition Leads to Cross-Request Data Leakage
Diese Seite enthält Fakten aus öffentlichen Sicherheitsquellen. Lesen Sie vor dem Aktualisieren die Originalmeldung.
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Angular uses a DI container (the "platform injector") to hold request-specific state during server-side rendering. For historical reasons, the container was stored as a JavaScript module-scoped global variable. When multiple requests are processed concurrently, they could inadvertently share or overwrite the global injector state. In practical terms, this can lead to one request responding with data meant for a completely different request, leaking data or tokens included on the rendered page or in response headers. As long as an attacker had network access to send any traffic that received a rendered response, they may have been able to send a large number of requests and then inspect the responses for information leaks. The APIs `bootstrapApplication`, `getPlatform`, and `destroyPlatform` were vulnerable and required SSR-only breaking changes. The issue has been patched in all active release lines as well as in the v21 prerelease. Patched packages include `@angular/platform-server` 21.0.0-next.3, 20.3.0, 19.2.15, and 18.2.14 and `@angular/ssr` 21.0.0-next.3, 20.3.0, 19.2.16, and 18.2.21. Several workarounds are available. Disable SSR via Server Routes or builder options, remove any asynchronous behavior from custom `bootstrap` functions, remove uses of `getPlatform()` in application code, and/or ensure that the server build defines `ngJitMode` as false.
CVSS 7.1 · Hoch · EPSS 0,4% · Korrektur verfügbar
- Veröffentlicht
- Aktualisiert
Technologie-Stack: node
Betroffene Produkte und Versionen
angular
- Softwareversionen
- @angular/platform-server >= 16.0.0-next.0, < 18.2.14: Betroffen
- @angular/platform-server >= 20.0.0-next.0, < 20.3.0: Betroffen
- @angular/platform-server >= 19.0.0-next.0, < 19.2.15: Betroffen
- @angular/platform-server >= 21.0.0-next.0, < 21.0.0-next.3: Betroffen
- @angular/ssr >= 17.0.0-next.0, < 18.2.21: Betroffen
- @angular/ssr >= 19.0.0-next.0, < 19.2.16: Betroffen
- @angular/ssr >= 20.0.0-next.0, < 20.3.0: Betroffen
- @angular/ssr >= 21.0.0-next.0, < 21.0.0-next.3: Betroffen
- @nguniversal/common >= 16.0.0-next.0, <= 16.2.0: Betroffen
Keine Korrektur veröffentlicht
@angular/platform-server npm
- Betroffene Versionsbereiche
- SEMVER: ≥ 16.0.0-next.0, < 18.2.14
Auf 18.2.14 aktualisieren
@angular/platform-server npm
- Betroffene Versionsbereiche
- SEMVER: ≥ 20.0.0-next.0, < 20.3.0
Auf 20.3.0 aktualisieren
@angular/platform-server npm
- Betroffene Versionsbereiche
- SEMVER: ≥ 19.0.0-next.0, < 19.2.15
Auf 19.2.15 aktualisieren
@angular/platform-server npm
- Betroffene Versionsbereiche
- SEMVER: ≥ 21.0.0-next.0, < 21.0.0-next.3
Auf 21.0.0-next.3 aktualisieren
@angular/ssr npm
- Betroffene Versionsbereiche
- SEMVER: ≥ 17.0.0-next.0, < 18.2.21
Auf 18.2.21 aktualisieren
@angular/ssr npm
- Betroffene Versionsbereiche
- SEMVER: ≥ 19.0.0-next.0, < 19.2.16
Auf 19.2.16 aktualisieren
@angular/ssr npm
- Betroffene Versionsbereiche
- SEMVER: ≥ 20.0.0-next.0, < 20.3.0
Auf 20.3.0 aktualisieren
@angular/ssr npm
- Betroffene Versionsbereiche
- SEMVER: ≥ 21.0.0-next.0, < 21.0.0-next.3
Auf 21.0.0-next.3 aktualisieren
@nguniversal/common npm
- Betroffene Versionsbereiche
- SEMVER: ≥ 16.0.0-next.0, ≤ 16.2.0
Keine Korrektur veröffentlicht