-
Notifications
You must be signed in to change notification settings - Fork 35
Security advisory "Prototype Pollution" #48
Comments
Noticed this as well. It seems lodash has been removed as a dependency from the GitHub version of this package, but that the version number hasn't been incremented since then / no new package has been published? (https://github.com/jamestalmage/cli-table2/pull/27/files) If I do |
And that was back in 2016..... |
I made a quick fix for this issue. This is only for version 0.2.0. The unreleased state of the code is not using lodash at all as it seems to me. To fix this for you, you can add a "resolutions" area in your package.json with my fork as long as the pull request is not merged. Sorry for the typos in the branch name, i was in a hurry...
|
@jamestalmage Should we release a new version to |
as you can see in #43 we have forked the project to https://github.com/cli-table/cli-table3 and have published a new |
Nice... if only we can get npm to switch to cli-table3 :) |
You can for your own with a resolutions block, as i stated above, but for npm itself, all packages have to change their dependencies. |
wasn't aware that npm uses it, but I guess we can send them a PR that updates the dependency update: npm/npm#20955 😉 |
I think the big offender is |
@codemonkeyking the problem was the old version of lodash. cli-table3 is no longer using it, so there is no issue anymore. |
0.2.0 has a security advisory applicable.
https://nodesecurity.io/advisories/577
The text was updated successfully, but these errors were encountered: