GHSA-GXX4-3XCV-F8QX
@angular/platform-server: Missing `<noscript>` Raw-Text Serialization Escaping leads to Cross-Site Scripting (XSS) in Angular SSR
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 22.0.0-rc.2 | @angular/platform-server · -18 d desde divulgación | |
| Remediación | Parche 19.2.25 | @angular/platform-server · -13 d desde divulgación | |
| Remediación | Parche 20.3.24 | @angular/platform-server · -13 d desde divulgación | |
| Remediación | Parche 21.2.16 | @angular/platform-server · -12 d desde divulgación | |
| Divulgación | Publicada | GHSA-GXX4-3XCV-F8QX divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
A Cross-Site Scripting (XSS) vulnerability exists in `@angular/platform-server`'s DOM emulation dependency (`domino`) when serializing the content of `<noscript>` elements.
When rendering dynamic text content inside a `<noscript>` element via template bindings (such as `{{ value }}` or `[textContent]`), the template engine expects the browser to render the content safely. Under Server-Side Rendering (SSR), `domino` is configured with scripting enabled, meaning `<noscript>` is treated as a raw-text element.
However, `domino`'s serializer completely omitted `<noscript>` from the list of raw-text elements requiring closing-tag escaping during DOM serialization. As a result, any occurrence of `</noscript>` in the bound dynamic text was never escaped under any circumstances.
The unescaped closing tag was serialized directly into the output HTML (e.g. `<noscript></noscript><script>alert(1)</script></noscript>`). When parsed by a browser, it closes the `<noscript>` block early, allowing the injected `<script>` block to execute in the user's browser context, causing same-origin Cross-Site Scripting (XSS).
Impact
This vulnerability allows an attacker to perform same-origin Cross-Site Scripting (XSS) attacks against any user visiting an SSR-rendered page that binds user-controlled data inside a `<noscript>` element. This can lead to session hijacking, credentials theft, unauthorized actions on behalf of users, and defacement.
Patched Versions
- 22.0.0-rc.2
- 21.2.16
- 20.3.24
- 19.2.25
Workarounds
If you cannot immediately update your dependencies, you can:
- Avoid binding user-controlled values inside `<noscript>` elements.
- Sanitize any user input placed inside `<noscript>` to explicitly strip closing `</noscript>` tags before passing it to the template.
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.25, 20.3.24, 21.2.16, 22.0.0-rc.2 | -13 d · -13 d · -12 d · -18 d | 22.2.6 no afectada |
19.2.2520.3.2421.2.1622.0.0-rc.2Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/angular/angular/security/advisories/GHSA-gxx4-3xcv-f8qxhttps://github.com/angular/angular/issues/68903https://github.com/angular/domino/pull/29https://github.com/angular/angularLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
