-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Current release of @vue/cli-service is affected by CVE-2021-27290 Regular Expression Denial of Service in ssri #6424
Comments
My pipeline has been failing since yesterday and I tried with both here's the npm audit report# npm audit report
ssri 5.2.2 - 6.0.1 || 7.0.0 - 8.0.0
Severity: moderate
Regular Expression Denial of Service - https://npmjs.com/advisories/565
fix available via `npm audit fix --force`
Will install @vue/[email protected], which is a breaking change
node_modules/@vue/cli-service/node_modules/ssri
node_modules/ssri
@vue/cli-service 4.0.0-alpha.0 - 4.5.12
Depends on vulnerable versions of ssri
Depends on vulnerable versions of terser-webpack-plugin
node_modules/@vue/cli-service
cacache 10.0.4 - 11.0.0 || 13.0.0 - 14.0.0
Depends on vulnerable versions of ssri
node_modules/@vue/cli-service/node_modules/cacache
terser-webpack-plugin 2.1.1 - 2.3.8
Depends on vulnerable versions of cacache
node_modules/@vue/cli-service/node_modules/terser-webpack-plugin
4 moderate severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force It seems to be caused by dependencies to FYI |
yeah we have the same problem, also see npm/ssri#20 |
Same problem, and similar npm audit report as @undergroundwires. Is it safe to proceed creating a project with these warnings? |
Same here. I tried to install ssri with npm from my own. But the vulnerabilities are the same. |
I Have now 3 ssri installed. 6.0.1 7.1.0 7.0.0 and 8.0.1. |
|
@dawwad Thank you. I tried, but no luck:
I removed yargs-parser from resolutions because i don't think it's part of this solution? Or didn't i understand correctly and do i need to include that as well? |
hey, @gerbenvandekraats, regarding yargs-yarser i had a low vulnerability as well, but yes it's not part of this solution.
this is my
|
hi guys, anyone looking at this? |
Needs to downgrade terser-webpack-plugin to v1, which is the default version in webpack 4. Since the major breaking changes in v2 are mostly related to option default values, the downgrading does not introduce breaking changes in Vue CLI. Closes #6424
Needs to downgrade terser-webpack-plugin to v1, which is the default version in webpack 4. Since the major breaking changes in v2 are mostly related to option default values, the downgrading does not introduce breaking changes in Vue CLI. Closes #6424
The |
Version
4.5.12
Environment info
Steps to reproduce
What is expected?
The latest version of the software does not report any vulnerabilities.
What is actually happening?
The latest version of the software has two vulnerabilities from ssri, one from a direct dependency on the package.
My pipeline broke today once this vulnerability finally made it into the audit database.
https://www.npmjs.com/advisories/565
The text was updated successfully, but these errors were encountered: