Angular Client Hydration DOM Clobbering & Response-Cache Poisoning
angular
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @angular/core npm |
|
|
angular
| Product | Affected | Fixed in |
|---|---|---|
| @angular/core 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, to optimize client-side bootstrap in Server-Side Rendered (SSR) environments, Angular supports Hydration via provideClientHydration(). During SSR, Angular serializes the application's runtime state (such as cached HttpClient responses) and outputs it into the HTML stream as a <script> tag with a predictable identifier. During client bootstrap, Angular recovers this state by looking up the element via document.getElementById('ng-state') and parsing its text content. Because the DOM element lookup for the state container is predictable and relies solely on the ID selector (ng-state), it is susceptible to DOM Clobbering. If the application binds untrusted user input or CMS content to element properties such as id (e.g., <div [id]="userInput"> or <a id="ng-state">) before the genuine <script> tag is parsed by the browser, the attacker-controlled element takes precedence in the DOM lookup. During hydration, when Angular calls document.getElementById('ng-state'), the browser returns the attacker's clobbered element. Angular then attempts to parse the text content or attributes of this clobbered element as JSON. This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.
From the CVE record · GitHub_M
Angular client hydration looks up serialized application state using the predictable `ng-state` element ID. If an application renders attacker-controlled content with that ID before the genuine state script, Angular may parse the attacker-controlled element instead. The input does not specify whether authentication or user interaction is required.
Teams using affected npm `@angular/core` versions (22.0.0-next.0 to before 22.0.1, 21.0.0-next.0 to before 21.2.17, 20.0.0-next.0 to before 20.3.25, or 19.2.25 and earlier) should check applications using SSR hydration.