Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server
angular
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @angular/platform-server npm |
|
|
angular
| Product | Affected | Fixed in |
|---|---|---|
| @angular/platform-server npm |
|
|
19.2.21Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.21, 20.3.19, 21.2.9, and 22.0.0-next.8, a Server-Side Request Forgery (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. This issue has been patched in versions 19.2.21, 20.3.19, 21.2.9, and 22.0.0-next.8.
From the CVE record · GitHub_M
Improper URL handling in @angular/platform-server during server-side rendering can let a network attacker make the application treat an attacker-controlled domain as its origin. If the application makes relative HttpClient requests or uses PlatformLocation.hostname, those references can be redirected to the attacker's server, potentially exposing internal APIs or metadata services. No authentication or user interaction is described.
Teams running server-side rendering with npm @angular/platform-server should check versions >=22.0.0-next.0 <22.0.0-next.8, >=21.0.0-next.0 <21.2.9, >=20.0.0-next.0 <20.3.19, >=19.0.0-next.0 <19.2.21, or <=18.2.14.