-
-
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
Upgrade Dependency "minimist" to avoid prototype pollution security risk #5285
Comments
Yup, same problem |
Same issue is also present for |
Same issue present for the following;
|
Same issue. |
But the depended version is a caret range: |
Can someone provide the exact steps on how to do this the right way? |
Running |
I don't see how The mocha and cypress ones are addressed in mochajs/mocha#4204 cypress-io/cypress#6726 So please use the |
The above workaround did work for me like so: package.json:
I then ran |
…ory with package.json resolutions -Mentioned security advisory: https://www.npmjs.com/advisories/1179 -Fix for mentioned security advisory: vuejs/vue-cli#5285 (comment)
Version
4.2.3
Reproduction link
n/a
Environment info
Steps to reproduce
This issue can be easily found using npm tooling. I am not sure how to identify it using yarn. Basically, just run "npm audit" or "npm audit --fix". The minimist package is recognized to have a prototype pollution vulnerability and it is recommended to move up to version 1.2.3 or higher.
What is expected?
No security vulnerabilities
What is actually happening?
npm flags vue-cli as harboring a moderate risk (prototype pollution) through the "minimist" dependency.
I tried to fix this myself, but was unable to push my code up for a PR. It should be as simple as updating the line in package.json. However tests will need to be run to ensure that doing so does not introduce any other problems.
The text was updated successfully, but these errors were encountered: