Skip to content
This repository has been archived by the owner on Jun 15, 2019. It is now read-only.

Security advisory "Prototype Pollution" #48

Open
sidhuko opened this issue May 8, 2018 · 10 comments
Open

Security advisory "Prototype Pollution" #48

sidhuko opened this issue May 8, 2018 · 10 comments

Comments

@sidhuko
Copy link

sidhuko commented May 8, 2018

0.2.0 has a security advisory applicable.

https://nodesecurity.io/advisories/577

@dogboydog
Copy link

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 npm pack cli-table2 I get a package with lodash included in the dependencies, different from the current master

@NorthernMan54
Copy link

And that was back in 2016.....

@stanglt
Copy link

stanglt commented May 9, 2018

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...

[...]
  "resolutions": {
    "cli-table2": "https://github.com/civilatio/cli-table2.git#protypePolutionFix"
  },
[...]

taichi added a commit to taichi/ci-yarn-upgrade that referenced this issue May 10, 2018
@thomasyuan
Copy link

@jamestalmage Should we release a new version to fix this non-exist issue?

@Turbo87
Copy link
Contributor

Turbo87 commented Jun 10, 2018

as you can see in #43 we have forked the project to https://github.com/cli-table/cli-table3 and have published a new [email protected] release for the current master branch :)

@mkj28
Copy link

mkj28 commented Jun 10, 2018

Nice... if only we can get npm to switch to cli-table3 :)

@stanglt
Copy link

stanglt commented Jun 11, 2018

You can for your own with a resolutions block, as i stated above, but for npm itself, all packages have to change their dependencies.

@Turbo87
Copy link
Contributor

Turbo87 commented Jun 11, 2018

wasn't aware that npm uses it, but I guess we can send them a PR that updates the dependency

update: npm/npm#20955 😉

@codemonkeyking
Copy link

I think the big offender is nsp itself. This isn't even required as a real dependency for me but it gets flagged by the security warning via nsp.

@Turbo87
Copy link
Contributor

Turbo87 commented Jun 20, 2018

@codemonkeyking the problem was the old version of lodash. cli-table3 is no longer using it, so there is no issue anymore.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants