Angular SSR: Denial of Service (DoS) via Infinite Loop on Malformed DOCTYPE
angular · @angular/ platform-server
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @angular/platform-server npm |
|
|
angular · @angular/ platform-server
| Product | Affected | Fixed in |
|---|---|---|
| @angular/platform-server npm |
|
|
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.31, 21.2.23, and 22.1.6, the @angular/platform-server DOM emulation parser can enter an infinite synchronous loop when Angular server-side rendering processes attacker-controlled HTML containing an incomplete DOCTYPE that ends with whitespace at end of input. In Domino lib/HTMLParser.js, after_doctype_name_state emits doctype and EOF tokens without advancing nextchar or leaving the fixed-lookahead state, so the scanner repeatedly handles the same EOF marker. A remote unauthenticated attacker can use this condition through server-side HTML parsing paths such as innerHTML binding to consume a Node.js SSR worker at full CPU, starve the event loop, and stop concurrent and subsequent requests. This issue is fixed in versions 20.3.31, 21.2.23, and 22.1.6.
From the CVE record · GitHub_M
The @angular/platform-server DOM emulation parser can enter an infinite loop when server-side rendering processes attacker-controlled HTML with an incomplete DOCTYPE ending in whitespace. A remote, unauthenticated attacker can trigger this through a server-side HTML parsing path, consuming a Node.js SSR worker at full CPU and blocking requests; no user interaction is required.
Teams running Angular server-side rendering with @angular/platform-server versions <=19.2.25, >=20.0.0 <20.3.31, >=21.0.0 <21.2.23, or >=22.0.0 <22.1.6 should check their deployments.