-
Notifications
You must be signed in to change notification settings - Fork 63
posibility of a 1.7.2 release with updated majo #179
Description
Hi, @egoist,
Issue Description
I noticed that a vulnerability is introduced in sao@1.7.1:
Vulnerability CVE-2020-28469 affects package glob-parent (versions:<5.1.2): https://snyk.io/vuln/SNYK-JS-GLOBPARENT-1016905
The above vulnerable package is referenced by sao@1.7.1 via:
sao@1.7.1 ➔ majo@0.6.3 ➔ fast-glob@2.2.7 ➔ glob-parent@3.1.0
Since sao@1.7.1 (36,523 downloads per week) is referenced by 55 downstream projects (e.g., create-factor-app 1.8.26 (latest version), create-nuxt-app 3.7.1 (latest version), @dpc-sdp/create-ripple-app 1.23.1 (latest version), create-nuxt-content-docs 0.4.6 (latest version), bhkk-cna 0.0.27 (latest version)), the vulnerability CVE-2020-28469 can be propagated into these downstream projects and expose security threats to them via the following package dependency paths:
(1)tmt@1.0.15 ➔ tmt-init@1.0.9 ➔ sao@1.7.1 ➔ majo@0.6.3 ➔ fast-glob@2.2.7 ➔ glob-parent@3.1.0
(2)ddun-cli@0.0.3 ➔ ddun-generator-framework@0.0.6 ➔ sao@1.7.1 ➔ majo@0.6.3 ➔ fast-glob@2.2.7 ➔ glob-parent@3.1.0
......
If sao@1.7.* 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 sao@1.7.1 ?
Fixing suggestions
In sao@1.7.2, maybe you can kindly try to perform the following upgrade(not crossing major version) :
majo ^0.6.2 ➔ ^0.9.0;
Note:
majo@0.9.0(>=0.9.0) transitively depends on glob-parent@5.1.2 which has fixed the vulnerability CVE-2020-28469.
Of course, you are welcome to share other ways to resolve the issue.
Best regards,
^_^