You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First and foremost, thank you kindly for the work and maintenance of forever-monitor!
We are working through updates of our system and have a need to address security vulnerabilities with tar which come in by way of forever-monitor's dependency on an older version of Chokidar. It looks like the latest Chokidar (3.5.2) would address the issue described by evansrobert as well as the issue for tar.
The PR #198 looks like it could be a good basis for maintaining backwards compatibility with Node < 8 while supporting Chokidar 3 on modern versions of Node.. with a minor version bump on this PR (to Chokidar 3.5.2) maybe it could address all of the CVE's showing up?
I'd be happy to help in some way if a new PR is needed.
Hi, @kibertoad,
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]
Since [email protected] (138,256 downloads per week) is referenced by 25 downstream projects (e.g., forever 4.0.1 (latest version), domotz-remote-pawn 3.9.0-b001 (latest version), alks 3.5.0 (latest version), gulp-forever-monitor 1.0.9 (latest version), edgemicro 3.2.2 (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]
(2)
[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 :
chokidar ^2.1.8 ➔ ^3.0.0
;Note:
[email protected](>=3.0.0) directly depends on [email protected] which has fixed the vulnerability CVE-2020-28469.
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: