Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 19.2.21, 20.3.19, 21.2.9, 22.0.0-next.8
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Angular 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- angular angular
fixed in 19.2.21; From 20.0.0-next.0 · fixed in 20.3.19; From 21.0.0-next.0 · fixed in 21.2.9; From 22.0.0-next.0 · fixed in 22.0.0-next.8
- @angular/platform-servernpm
From 22.0.0-next.0 · fixed in 22.0.0-next.8
- @angular/platform-servernpm
From 21.0.0-next.0 · fixed in 21.2.9
- @angular/platform-servernpm
From 20.0.0-next.0 · fixed in 20.3.19
- @angular/platform-servernpm
From 19.0.0-next.0 · fixed in 19.2.21
- @angular/platform-servernpm
through 18.2.14