GHSA-45Q2-GJVG-7973
Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 19.2.21 | @angular/platform-server · -1 d desde divulgación | |
| Remediación | Parche 20.3.19 | @angular/platform-server · -1 d desde divulgación | |
| Remediación | Parche 21.2.9 | @angular/platform-server · -1 d desde divulgación | |
| Remediación | Parche 22.0.0-next.8 | @angular/platform-server · -1 d desde divulgación | |
| Divulgación | Publicada | GHSA-45Q2-GJVG-7973 divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
Impact
A Server-Side Request Forgery (SSRF) https://developer.mozilla.org/en-US/docs/Web/Security/Attacks/SSRF vulnerability exists in `@angular/platform-server` due to improper handling of URLs during Server-Side Rendering (SSR).
When an attacker sends a request such as `GET /\evil.com/ HTTP/1.1` the server engine (Express, etc.) passes the URL string to Angular’s rendering functions.
Because the URL parser normalizes the backslash to a forward slash for HTTP/HTTPS schemes, the internal state of the application is hijacked to believe the current origin is `evil.com`. This misinterpretation tricks the application into treating the attacker’s domain as the local origin. Consequently, any relative `HttpClient` requests or `PlatformLocation.hostname` references are redirected to the attacker controlled server, potentially exposing internal APIs or metadata services.
Affected APIs:
- `renderModule`
- `renderApplication`
- `CommonEngine` (from `@angular/ssr`)
Non-Affected APIs:
- `AngularAppEngine` (from `@angular/ssr`)
- `AngularNodeAppEngine` (from `@angular/ssr`)
### Attack Preconditions
- The server has outbound network access.
- The application uses Angular SSR via the affected APIs.
- A pathname is passed as URL to the rendering method (e.g. using `req.url`).
- The server-side code performs HTTP requests using `HttpClient` with relative URLs or uses `PlatformLocation.hostname` to build URLs.
### Patches
- 22.0.0-next.8
- 21.2.9
- 20.3.19
- 19.2.21
### Workarounds
Developers should implement a middleware to sanitize the request URL before it reaches Angular. This involves stripping or normalizing leading slashes:
app.use((req, res, next) => {
// Sanitize the URL to ensure it starts with a single forward slash
if (req.url.startsWith('//') || req.url.startsWith('/\\') || req.url.startsWith('\\')) {
req.url = '/' + req.url.replace(/^[/\\]+/, '');
}
next();
});
### References
- Fix https://github.com/angular/angular/pull/68194
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npm@angular/platform-server |
Corregida | 19.2.21, 20.3.19, 21.2.9, 22.0.0-next.8 | -1 d · -1 d · -1 d · -1 d | 22.2.6 no afectada |
19.2.2120.3.1921.2.922.0.0-next.8Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-41423https://github.com/angular/angular/security/advisories/GHSA-45q2-gjvg-7973https://github.com/angular/angular/pull/68194https://github.com/angular/angular/commit/ede7c58a2aa13fdccc8f0b67ce93ba1c11749412https://github.com/angular/angularLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
