posibility of a 2.9.1 release with less strict yargs version dependency

[evansrobert]

Hi, @atian25 @fengmk2, there is a vulnerability introduced by package ** yargs-parser@11.1.1**:

Issue Description

I noticed that a vulnerability is introduced in common-bin@2.9.0:
Vulnerability CVE-2020-7608 affects package yargs-parser (versions:>5.0.0-security.0 <5.0.1,>=6.0.0 <13.1.2,>=14.0.0 <15.0.1,>=16.0.0 <18.1.1): https://snyk.io/vuln/SNYK-JS-YARGSPARSER-560381
The above vulnerable package is referenced by common-bin@2.9.0 via:
common-bin@2.9.0 ➔ yargs@12.0.5 ➔ yargs-parser@11.1.1

Since common-bin@2.9.0 (36,523 downloads per week) is referenced by 68 downstream projects (e.g., egg-scripts 2.14.0 (latest version), egg-bin 4.16.4 (latest version), surgio 2.9.1 (latest version), cabloy 4.11.16 (latest version), midway-bin 1.20.3 (latest version)), the vulnerability CVE-2020-7608 can be propagated into these downstream projects and expose security threats to them via the following package dependency paths:
(1)macaca-datahub@3.2.0 ➔ egg-scripts@2.14.0 ➔ common-bin@2.9.0 ➔ yargs@12.0.5 ➔ yargs-parser@11.1.1
(2)sparrow-server@0.9.27 ➔ egg-scripts@2.14.0 ➔ common-bin@2.9.0 ➔ yargs@12.0.5 ➔ yargs-parser@11.1.1
......

If common-bin@2.9.0 removes the vulnerable package from the above version, then its fixed version can help downstream users decrease their pain.

Given the large number of downstream users, could you help update your package to remove the vulnerability from common-bin@2.9.0 ?

Fixing suggestions

In common-bin@2.9.1, maybe you can kindly try to perform the following upgrade :
yargs ^12.0.2 ➔ ^13.1.0;

Note:
yargs@13.1.0(>=13.1.0 <14.1.0) directly depends on yargs-parser@13.1.2 which has fixed the vulnerability CVE-2020-7608.

Thank you for your attention to this issue and welcome to share other ways to resolve the issue.^_^

[WinfredWang]

same issue. please handle it. Thanks

[fengmk2]

Will fix this soon.