Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)
angular
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @angular/core npm |
|
|
angular
| Product | Affected | Fixed in |
|---|---|---|
| @angular/core npm |
|
|
20.3.22Angular 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.23, an issue in the @angular/core package allows bypassing script-execution restrictions during dynamic component creation. Specifically, the dynamic component instantiation mechanism (createComponent) failed to reject mounting components directly onto a <script> or namespaced script element (such as <svg:script>). This enabled the initialization of custom components on a tag that executes scripts, allowing attackers to hijack or inject script-executing hosts. This flaw enables an attacker who can control the host element or selector parameter passed to createComponent to initialize or mount an Angular component directly onto a <script> tag, leading to execution of untrusted code or 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.23.
From the CVE record · GitHub_M
The @angular/core createComponent mechanism can mount a component onto a <script> or namespaced script element. An attacker who can control the host element or selector passed to createComponent may execute untrusted code in the client.
Teams using npm @angular/core should check installations in the affected ranges: <=18.2.14, >=19.0.0-next.0 <19.2.23, >=20.0.0-next.0 <20.3.22, >=21.0.0-next.0 <21.2.15, or >=22.0.0-next.0 <22.0.0-rc.2.