Angular SSR has an Open Redirect via X-Forwarded-Prefix
angular-cli
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @angular/ssr npm |
|
|
angular-cli
| Product | Affected | Fixed in |
|---|---|---|
| @angular/ssr npm |
|
|
The Angular SSR is a server-rise rendering tool for Angular applications. An Open Redirect vulnerability exists in the internal URL processing logic in versions on the 19.x branch prior to 19.2.21, the 20.x branch prior to 20.3.17, and the 21.x branch prior to 21.1.5 and 21.2.0-rc.1. The logic normalizes URL segments by stripping leading slashes; however, it only removes a single leading slash. When an Angular SSR application is deployed behind a proxy that passes the `X-Forwarded-Prefix` header, an attacker can provide a value starting with three slashes. This vulnerability allows attackers to conduct large-scale phishing and SEO hijacking. In order to be vulnerable, the application must use Angular SSR, the application must have routes that perform internal redirects, the infrastructure (Reverse Proxy/CDN) must pass the `X-Forwarded-Prefix` header to the SSR process without sanitization, and the cache must not vary on the `X-Forwarded-Prefix` header. Versions 21.2.0-rc.1, 21.1.5, 20.3.17, and 19.2.21 contain a patch. Until the patch is applied, developers should sanitize the `X-Forwarded-Prefix` header in their`server.ts` before the Angular engine processes the request.
From the CVE record · GitHub_M
Angular SSR has an open redirect in its internal URL processing. A remote attacker can exploit it for phishing or SEO hijacking if the application has routes with internal redirects, a proxy passes an unsanitized X-Forwarded-Prefix header, and the cache does not vary on that header. No authentication or user interaction is specified.
Check applications using npm @angular/ssr in the affected 19.x, 20.x, or 21.x ranges, including prereleases.