Angular
Angular: SSR XSS via Unescaped Processing Instruction (<?...?>) Nodes in Fallback Raw-Content Elements
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.30, 21.2.22, and 22.1.4, Angular server-side rendering (SSR) in @angular/platform-server serializes ProcessingInstruction DOM nodes inside fallback raw-content elements without escaping matching ancestor closing tags. ProcessingInstruction data escaped greater-than characters but left less-than characters untouched and did not inspect fallback ancestors, so data such as a matching closing tag prematurely terminates noscript, iframe, noembed, or noframes containers. The vulnerable nodes cannot be authored through standard Angular templates; reachability requires application or library code using inject(DOCUMENT).createProcessingInstruction with attacker-controlled data or Renderer2 DOM insertion inside a fallback container. In HTML5 RAWTEXT parsing, the premature close causes subsequent sibling elements to be interpreted as live HTML and enables arbitrary JavaScript execution in a victim's browser. This issue is fixed in versions 20.3.30, 21.2.22, and 22.1.4.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- <= 19.2.25
- >= 20.0.0, < 20.3.30
- >= 21.0.0, < 21.2.22
- >= 22.0.0, < 22.1.4
Fixed in 20.3.30, 21.2.22, 22.1.4
Mitigation
Upgrade angular to 20.3.30 or 21.2.22 or 22.1.4 or later.
References
- Vendor advisory github.com/angular/angular/security/advisories…
- Patch github.com/angular/angular/commit/73d8bbd27cb4…
- Patch github.com/angular/angular/commit/89b20568dfae…
5 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.