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

posibility of a 2.9.1 release with less strict yargs version dependency #46

Closed
evansrobert opened this issue Aug 19, 2021 · 2 comments · Fixed by #48
Closed

posibility of a 2.9.1 release with less strict yargs version dependency #46

evansrobert opened this issue Aug 19, 2021 · 2 comments · Fixed by #48
Assignees
Labels

Comments

@evansrobert
Copy link

Hi, @atian25 @fengmk2, there is a vulnerability introduced by package ** [email protected]**:

Issue Description

I noticed that a vulnerability is introduced in [email protected]:
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 [email protected] via:
[email protected][email protected][email protected]

Since [email protected] (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)[email protected][email protected][email protected][email protected][email protected]
(2)[email protected][email protected][email protected][email protected][email protected]
......

If [email protected] 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 [email protected] ?

Fixing suggestions

In [email protected], maybe you can kindly try to perform the following upgrade :
yargs ^12.0.2 ➔ ^13.1.0;

Note:
[email protected](>=13.1.0 <14.1.0) directly depends on [email protected] 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
Copy link

same issue. please handle it. Thanks

@fengmk2 fengmk2 self-assigned this Feb 9, 2022
@fengmk2 fengmk2 added the bug label Feb 9, 2022
@fengmk2
Copy link
Member

fengmk2 commented Feb 9, 2022

Will fix this soon.

fengmk2 added a commit that referenced this issue Feb 9, 2022
fengmk2 added a commit that referenced this issue Feb 9, 2022
fengmk2 added a commit that referenced this issue Feb 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants