GHSA-JHPW-976M-542J
Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 22.0.2 | @angular/common · -47 d desde divulgación | |
| Remediación | Parche 20.3.27 | @angular/common · -5 d desde divulgación | |
| Remediación | Parche 21.2.19 | @angular/common · -5 d desde divulgación | |
| Divulgación | Publicada | GHSA-JHPW-976M-542J divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
Angular's `HttpTransferCache` caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration.
During SSR, `HttpTransferCache` previously generated identical key material for distinct request parameters when repeated values were present because repeated values were joined with commas:
new HttpParams().set('role', 'user,admin')
new HttpParams().append('role', 'user').append('role', 'admin')Both requests previously serialized as `role=user,admin`, allowing distinct `HttpClient` requests to produce the same transfer-cache key material.
Impact
In an SSR application, this cache-key ambiguity can make a later security-sensitive `HttpClient` request receive the response from an earlier semantically different request in the same render. For example, an attacker-influenced scalar-comma request can be cached and then replayed as the response for a trusted repeated-param authorization or data request to the same URL. As a result, Angular's server-rendered output can be based on the wrong backend response because the trusted request is not dispatched. This can lead to:
- State Poisoning: Using incorrect or attacker-influenced cached responses for subsequent application logic.
- Cross-Request Response Reuse: Reusing cached responses across requests with semantically different parameters.
Patched Versions
- 22.0.2
- 21.2.19
- 20.3.27
Workarounds
If you cannot upgrade immediately, configure your `HttpClient` requests to skip transfer caching for sensitive endpoints where repeated parameter keys are used:
this.http.get('/api/resource', {
transferCache: false
});Alternatively, disable the HTTP transfer cache globally in your application bootstrap config:
import { provideClientHydration, withNoHttpTransferCache } from '@angular/platform-browser';
export const appConfig = {
providers: [
provideClientHydration(
withNoHttpTransferCache()
)
]
};Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npm@angular/common |
Corregida | 20.3.27, 21.2.19, 22.0.2 | -5 d · -5 d · -47 d | 22.2.6 no afectada |
20.3.2721.2.1922.0.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-jhpw-976m-542jhttps://github.com/angular/angular/pull/68571https://github.com/angular/angular/commit/6867f77ec779a0a24f6339ad6c775f444202103chttps://github.com/angular/angular/commit/948a8d6831e8920b54663ec79421da95210e0e35https://github.com/angular/angular/commit/a64e2883e9dc4abdac70209129be303de79e5b2bhttps://github.com/angular/angular/commit/a6c7fc5c13e6e494a4c9bd8e773b8d4b2a99b20chttps://github.com/angular/angularLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
