| Package | Affected versions | Patched versions |
|---|---|---|
| angular cli | = 22.0.0≥ 17.0.0, < 19.2.0≥ 20.0.0, ≤ 20.3.18≥ 21.0.0, < 21.2.4 | 19.2.021.2.4 |
| @angular/compiler | ≥ 17.0.0-next.0, ≤ 18.2.14≥ 19.0.0-next.0, < 19.2.20≥ 20.0.0-next.0.0.0, < 20.3.18≥ 21.0.0-next.0, < 21.2.4≥ 22.0.0-next.0, < 22.0.0-next.3 | 19.2.2020.3.1821.2.422.0.0-next.3 |
| @angular/core | ≥ 17.0.0-next.0, ≤ 18.2.14≥ 19.0.0-next.0, < 19.2.20≥ 20.0.0-next.0.0.0, < 20.3.18≥ 21.0.0-next.0, < 21.2.4≥ 22.0.0-next.0, < 22.0.0-next.3 | 19.2.2020.3.1821.2.422.0.0-next.3 |
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-<attribute> 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:
<a href="{{maliciousUrl}}" i18n-href>Click me</a>
The following attributes have been confirmed to be vulnerable:
actionbackgroundcitecodebasedataformactionhrefitemtypelongdescpostersrcxlink:hrefWhen exploited, this vulnerability allows an attacker to execute arbitrary code within the context of the vulnerable application's domain. This enables:
i18n-<name> attribute on the same element.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:
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site freeimport {Component, inject, SecurityContext} from '@angular/core';
import {DomSanitizer} from '@angular/platform-browser';
@Component({
template: `
<form action="{{url}}" i18n-action>
<button>Submit</button>
</form>
`,
})
export class App {
url: string;
constructor() {
const dangerousUrl = 'javascript:alert(1)';
const sanitizer = inject(DomSanitizer);
this.url = sanitizer.sanitize(SecurityContext.URL, dangerousUrl) || '';
}
}