Angular: Template and Attribute Namespace Sanitization Bypass (XSS)
- 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 21.2.15, 22.0.0-rc.2, 20.3.22, 19.2.22
- 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 22.0.0-rc.2, 21.2.15, 20.3.22 and 19.2.22, an issue in the @angular/compiler and @angular/core packages allows bypassing element and attribute sanitization/validation through specific namespace workarounds. Specifically, namespaced script elements (e.g., <svg:script> or <:svg:script>) were not properly identified as script elements by the Angular template preparser, allowing them to pass through template compilation without being stripped. Furthermore, security context schema mappings for element attributes did not consistently handle attributes within namespaced elements (like SVG and MathML), opening up gaps where malicious namespaced attributes could bypass runtime and compile-time sanitizers. Combined, these flaws enable an attacker who can inject or supply a template/tag structure with custom namespaces to bypass Angular's script-stripping logic and attribute sanitizers, leading to client-side Cross-Site Scripting (XSS). This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22 and 19.2.22.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- angular angular
through 18.2.14
- @angular/corenpm
From 21.0.0-next.0 · fixed in 21.2.15
- @angular/corenpm
From 22.0.0-next.0 · fixed in 22.0.0-rc.2
- @angular/corenpm
From 20.0.0-next.0 · fixed in 20.3.22
- @angular/corenpm
From 19.0.0-next.0 · fixed in 19.2.22
- @angular/corenpm
through 18.2.14
- @angular/compilernpm
From 21.0.0-next.0 · fixed in 21.2.15
- @angular/compilernpm
From 22.0.0-next.0 · fixed in 22.0.0-rc.2
- @angular/compilernpm
From 20.0.0-next.0 · fixed in 20.3.22
- @angular/compilernpm
From 19.0.0-next.0 · fixed in 19.2.22
- @angular/compilernpm
through 18.2.14