Angular: Two-Way Property Binding Sanitization Bypass (XSS)
angular
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @angular/compiler npm |
|
|
angular
| Product | Affected | Fixed in |
|---|---|---|
| @angular/compiler 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, an issue in the @angular/compiler package allows bypassing DOM property sanitization through the use of two-way property bindings. Specifically, when a native DOM property that requires sanitization (such as innerHTML, srcdoc, src, href, data, or sandbox) is bound using the two-way binding syntax (e.g., [(innerHTML)]="value" or bindon-innerHTML="value"), the Angular template compiler failed to apply the appropriate schema-derived sanitizer resolution to the TwoWayProperty operation. As a result, native two-way DOM bindings were emitted without the required sanitizer function, whereas equivalent one-way bindings would be properly sanitized. This flaw enables an attacker who can control the value of a two-way bound sensitive property to bypass Angular's built-in sanitization logic, potentially leading to client-side Cross-Site Scripting (XSS). This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.
From the CVE record · GitHub_M
The @angular/compiler template compiler fails to sanitize sensitive native DOM properties when they use two-way bindings. An attacker who can control a value bound this way can bypass Angular's sanitization, potentially causing client-side XSS. The input does not specify authentication requirements or whether additional user interaction is needed.
Teams using npm @angular/compiler versions >=22.0.0-next.0 <22.0.1, >=21.0.0-next.0 <21.2.17, >=20.0.0-next.0 <20.3.25, or <=19.2.25 should check their applications.