GHSA-g93w-mfhg-p222 Angular vulnerable to XSS in i18n attribute bindings

• npm @angular/core: >= 22.0.0-next.0, < 22.0.0-next.3 → fixed in 22.0.0-next.3 • npm @angular/core: >= 21.0.0-next.0, < 21.2.4 → fixed in 21.2.4 • npm @angular/core: >= 20.0.0-next.0.0.0, < 20.3.18 → fixed in 20.3.18 • npm @angular/core: >= 19.0.0-next.0, < 19.2.20 → fixed in 19.2.20 • npm @angular/core: >= 17.0.0-next.0, <= 18.2.14 (no fix yet) • npm @angular/compiler: >= 22.0.0-next.0, < 22.0.0-next.3 → fixed in 22.0.0-next.3 • npm @angular/compiler: >= 21.0.0-next.0, < 21.2.4 → fixed in 21.2.4 • npm @angular/compiler: >= 20.0.0-next.0.0.0, < 20.3.18 → fixed in 20.3.18 • npm @angular/compiler: >= 19.0.0-next.0, < 19.2.20 → fixed in 19.2.20 • npm @angular/compiler: >= 17.0.0-next.0, <= 18.2.14 (no fix yet)

A Cross-Site Scripting (XSS) vulnerability has been identified in the Angular runtime and compiler. It occurs when the application uses a security-sensitive attribute (for example href on an anchor tag) together with Angular's ability to internationalize attributes. Enabling internationalization for the sensitive attribute by adding `i18n-` name bypasses Angular's built-in sanitization mechanism, which when combined with a data binding to untrusted user-generated data can allow an attacker to inject a malicious script. The following example illustrates the issue: ```html Click me ``` The following attributes have been confirmed to be vulnerable: • `action` • `background` • `cite` • `codebase` • `data` • `formaction` • `href` • `itemtype` • `longdesc` • `poster` • `src` • `xlink:href` Impact When exploited, this vulnerability allows an attacker to execute arbitrary code within the context of the vulnerable application's domain. This enables: • Session Hijacking: Stealing session cookies and authentication tokens. • Data Exfiltration: Capturing and transmitting sensitive user data. • Unauthorized Actions: Performing actions on behalf of the user. Attack Preconditions 1. The application must use a vulnerable version of Angular. 2. The application must bind unsanitized user input to one of the attributes mentioned above. 3. The bound value must be marked for internationalization via the presence of a `i18n-` attribute on the same element. Patches • 22.0.0-next.3 • 21.2.4 • 20.3.18 • 19.2.20 Workarounds The primary workaround is to ensure that any data bound to the vulnerable attributes is never sourced from untrusted user input (e.g., database, API response, URL parameters) until the patch is applied, or when it is, it shouldn't be marked for internationalization. Alternatively, users can explicitly sanitize their attributes by passing them through Angular's `DomSanitizer`: ```ts import {Component, inject, SecurityContext} from '@angular/core'; import {DomSanitizer} from '@angular/platform-browser'; @Component({ template: ` Submit `, }) export class App { url: string; constructor() { const dangerousUrl = 'javascript:alert(1)'; const sanitizer = inject(DomSanitizer); this.url = sanitizer.sanitize(SecurityContext.URL, dangerousUrl) || ''; } } ``` References • Fix 1 • Fix 2