-
-
Notifications
You must be signed in to change notification settings - Fork 121
please update minimist due to prototype pollution (CVE-2020-7598) #316
Comments
Related to this issue in loader-fs-cache : viankakrisna/loader-fs-cache#5 |
I've publish a fork of https://www.npmjs.com/package/loader-fs-cache (repo https://github.com/viankakrisna/loader-fs-cache) to fix this issue here : https://www.npmjs.com/package/create-fs-cache (repo https://github.com/neokeld/create-fs-cache) |
@viankakrisna has published a new version (1.0.3) of loader-fs-cache with the fix. |
Fix webpack-contrib#316 updating loader-fs-cache min version. The new version of loader-fs-cache has support for a new version of minimist which has not the prototype pollution vuln (CVE-2020-7598).
I forked to see if this was an easy fix. Seems that the vulnerability is bubbling up from I assume there's no direct action to be taken here. |
Indeed it is also coming from standard-version,
There is an ongoing pull request on handlebars to fix this vuln : handlebars-lang/handlebars.js#1662 |
* Fix #316 updating loader-fs-cache min version Fix #316 updating loader-fs-cache min version. The new version of loader-fs-cache has support for a new version of minimist which has not the prototype pollution vuln (CVE-2020-7598). * fix: fix #316 update loader-fs-cache also in package-lock
It loks like @neokeld committed a fix but I don't see any new release version.. I took the work time to revisit this again now that I saw it was 'fixed' but it doesn't seem to be.. I installed latest.. |
@OZZlE I haven't launched yet |
Expected Behavior
npm audit
reports no vulnerabilities after installing this moduleActual Behavior
How Do We Reproduce?
npm i eslint-loader@latest
npm audit
The text was updated successfully, but these errors were encountered: