Skip to content
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

Vulnerability in yargs-parser 16.1.0 used in core and plugin-core-support #4775

Closed
mark-nc opened this issue May 29, 2020 · 1 comment · Fixed by #4777 or #4788
Closed

Vulnerability in yargs-parser 16.1.0 used in core and plugin-core-support #4775

mark-nc opened this issue May 29, 2020 · 1 comment · Fixed by #4777 or #4788

Comments

@mark-nc
Copy link

mark-nc commented May 29, 2020

Describe the bug
@kui-shell/core and @kui-shell/plugin-core-support both list yargs-parser v16.1.0 as a dependency.

This report describes a vulnerability in that version (see https://snyk.io/vuln/SNYK-JS-YARGSPARSER-560381). The vulnerability found shows that yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "proto" payload.

This vulnerability is fixed in these versions

  • yargs-parser 13.1.2
  • yargs-parser 15.0.1
  • yargs-parser 18.1.1 or higher

@kui-shell/core and @kui-shell/plugin-core-support should be updated to use version 18.1.1 or higher.

System

  • Kui version: 8.x
  • Operating system: any
starpit added a commit to starpit/kui that referenced this issue May 30, 2020
starpit added a commit that referenced this issue May 30, 2020
starpit added a commit to starpit/kui that referenced this issue Jun 1, 2020
starpit added a commit that referenced this issue Jun 1, 2020
starpit added a commit to starpit/kui that referenced this issue Jun 1, 2020
npm bug? somehow the last PR didn't update package-lock.json (despite changing it)

Fixes kubernetes-sigs#4775
@starpit
Copy link
Contributor

starpit commented Jun 1, 2020

weird npm bug? the prior PR indeed bumped the yargs-parser version to the desired 18.1.3, and it also indeed updated pafckage-lock.json... but for some reason npm ci still installed the old verison. worse, if one issued an npm install, one would get errors saying can't find yargs-parser. so weird.

@starpit starpit reopened this Jun 1, 2020
starpit added a commit that referenced this issue Jun 1, 2020
npm bug? somehow the last PR didn't update package-lock.json (despite changing it)

Fixes #4775
starpit added a commit to starpit/kui that referenced this issue Jun 1, 2020
npm bug? somehow the last PR didn't update package-lock.json (despite changing it)

Fixes kubernetes-sigs#4775
starpit added a commit that referenced this issue Jun 1, 2020
npm bug? somehow the last PR didn't update package-lock.json (despite changing it)

Fixes #4775
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants