First published: Thu May 26 2022(Updated: )
A vulnerability was found in Angular up to 11.0.4/11.1.0-next.2. It has been classified as problematic. Affected is the handling of comments. The manipulation leads to cross site scripting. It is possible to launch the attack remotely but it might require an authentication first. Upgrading to version 10.2.5, 11.0.5 or 11.1.0-next.3 is advised to to address this issue.
Credit: cna@vuldb.com
Affected Software | Affected Version | How to fix |
---|---|---|
npm/@angular/core | <10.2.5 | 10.2.5 |
npm/@angular/core | >=11.0.0<11.0.5 | 11.0.5 |
npm/@angular/core | >=11.1.0-next.0<=11.1.0-next.2 | 11.1.0-next.3 |
Angular | <11.0.5 | |
Angular | =11.1.0-next_0 | |
Angular | =11.1.0-next_1 | |
Angular | =11.1.0-next_2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-4231 is classified as a problematic vulnerability that can lead to cross-site scripting.
To remediate CVE-2021-4231, update to Angular core version 10.2.5 or 11.0.5 or later.
CVE-2021-4231 affects Angular versions up to 11.0.4 and 11.1.0-next.2.
Yes, CVE-2021-4231 can be exploited remotely, but it may require authentication first.
CVE-2021-4231 involves the handling of comments in Angular, leading to potential cross-site scripting attacks.