-
Notifications
You must be signed in to change notification settings - Fork 12k
13.3.8 build_angular uses vulnerable terser 5.11.0: CVE-2022-25858 #23593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Any updates on this issue? |
While this vulnerability doesn't apply to the Angular CLI as we don't expect maliciously crafted JS to be passed during the build We will be updating the version of terser in version 12 and 13. |
…-25858 While this vulnerability cannot be exploited through the Angular CLI as we don't expect it to be run on production servers. We update terser to remove the unnecessary vulnerability noise. Closes angular#23593
…-25858 While this vulnerability cannot be exploited through the Angular CLI as we don't expect it to be run on production servers. We update terser to remove the unnecessary vulnerability noise. Closes angular#23593 (cherry picked from commit 3d0b6fe)
…-25858 While this vulnerability cannot be exploited through the Angular CLI as we don't expect it to be run on production servers. We update terser to remove the unnecessary vulnerability noise. Closes angular#23593 (cherry picked from commit 3d0b6fe)
Closed via #23604 (comment) |
Why not in version 14? |
Because terser version 5.14.2 is already being used in version 14. |
Oh, I see. It is up to date on version 14.1.0 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25858
Hi,
is it possible to update terser in 13.3.x branch?
https://github.com/angular/angular-cli/blob/13.3.x/packages/angular_devkit/build_angular/package.json
Thanks!
The text was updated successfully, but these errors were encountered: