Angular: Sensitive Header Leakage on Cross-Origin Redirects in Angular Service Worker
angular
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @angular/service-worker npm |
|
|
angular
| Product | Affected | Fixed in |
|---|---|---|
| @angular/service-worker npm |
|
|
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.1, 21.2.17, and 20.3.25, an information disclosure vulnerability exists in the @angular/service-worker package of the Angular framework. When the Service Worker fetches assets, it preserves metadata (such as headers) from the original request. However, on cross-origin redirects, the Service Worker fails to strip sensitive headers, violating the Fetch redirect algorithm. This allows a remote attacker to obtain sensitive credentials (e.g., Authorization tokens, Proxy-Authorization credentials, or session cookies) by triggering a cross-origin redirect to an untrusted external origin. This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.
From the CVE record · GitHub_M
The Angular @angular/service-worker package can retain sensitive request headers when an asset fetch is redirected across origins. A remote attacker who triggers a cross-origin redirect to an untrusted origin can obtain credentials such as authorization tokens or session cookies. The input does not specify whether authentication or user interaction is required.
Teams using npm @angular/service-worker in versions >=22.0.0-next.0 <22.0.1, >=21.0.0-next.0 <21.2.17, >=20.0.0-next.0 <20.3.25, or <=19.2.25 should check their deployments.