Skip to content
This repository has been archived by the owner on Feb 5, 2022. It is now read-only.

posibility of a 1.7.2 release with updated majo #179

Open
evansrobert opened this issue Aug 19, 2021 · 0 comments
Open

posibility of a 1.7.2 release with updated majo #179

evansrobert opened this issue Aug 19, 2021 · 0 comments

Comments

@evansrobert
Copy link

Hi, @egoist,

Issue Description

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

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

Fixing suggestions

In [email protected], maybe you can kindly try to perform the following upgrade(not crossing major version) :
majo ^0.6.2 ➔ ^0.9.0;

Note:
[email protected](>=0.9.0) transitively depends on [email protected] which has fixed the vulnerability CVE-2020-28469.

Of course, you are welcome to share other ways to resolve the issue.

Best regards,
^_^

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant