We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, @atian25 @fengmk2, there is a vulnerability introduced by package ** [email protected]**:
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]
[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] ......
[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] ?
In [email protected], maybe you can kindly try to perform the following upgrade : yargs ^12.0.2 ➔ ^13.1.0;
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.^_^
The text was updated successfully, but these errors were encountered:
same issue. please handle it. Thanks
Sorry, something went wrong.
Will fix this soon.
🐛 FIX: Security fix for yargs
2dedb44
closes #46
67bc6f2
🐛 FIX: Security fix for yargs (#48)
7864b22
fengmk2
Successfully merging a pull request may close this issue.
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.^_^
The text was updated successfully, but these errors were encountered: