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
If wd removes the vulnerable package from the above versions, then its fixed versions can help downstream users decrease their pain.It’s kind of you to update packages in these versions.
Fixing suggestions
(1)In [email protected].*, you can kindly try to perform the following upgrade (not crossing its major versions): request ~2.55.0 ➔ 2.84.0;
Many active downstream users transitively use the lower versions of wd (@0.3.* and @0.2.* ) (introduced vulnerablities) via unmaintained packages (cannot update their dependencies).If [email protected].* ,@0.2.* can fix the issues, the vulnerable patches can be automatically propagated into the active downstream projects.
Hi @paimon0715 unfortunately this project isn't maintained. If you want to make the appropriate vuln fixes and submit as a PR, I'm happy to merge and publish a new version.
Hi @admc ,I’d like to report two vulnerabilities
Issue
There are two vulnerabilities (1 high and 1 low severity) introduced in wd.The details are as follows:
In [email protected].*:Vulnerability npmjs-advisories-1464 (high severity) is detected in package cryptiles(versions:>=0.0.1 <4.1.2):https://www.npmjs.com/advisories/1464
In [email protected].*: One is vulnerability npmjs-advisories-1464,the other is vulnerability CVE-2017-16137 (low severity),which is detected in package debug(versions:>=1.0.0 <2.6.9,>=3.0.0 <3.1.0):https://snyk.io/vuln/npm:debug:20170905
The above vulnerable packages are referenced by wd via:
1.
[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]
Solution
Since [email protected].* is transitively referenced by 83 downstream projects (e.g., gulp-metal 2.2.3 (latest version),duo 0.15.7 (latest version), duo-test 0.4.1 (latest version), grunt-mocha-webdriver 1.2.2 (latest version), skatejs-build 12.2.0(latest version)),
[email protected].* is referenced by 47 downstream projects (e.g., yiewd 0.6.0 (latest version), yeti 0.2.29 (latest version), yogi 0.1.13 (latest version), wd-sync 1.2.5 (latest version), awesome 0.0.7 (latest version)),
If wd removes the vulnerable package from the above versions, then its fixed versions can help downstream users decrease their pain.It’s kind of you to update packages in these versions.
Fixing suggestions
(1)In [email protected].*, you can kindly try to perform the following upgrade (not crossing its major versions):
request ~2.55.0 ➔ 2.84.0
;Note:
request 2.84.0 transitively depends on [email protected](a vulnerability npmjs-advisories-1464 patched version)
(2)In [email protected].*, you can kindly try to perform the following upgrades (not crossing their major versions):
request ~2.36.0 ➔ 2.84.0
;Note:
request 2.84.0 transitively depends on [email protected](a vulnerability npmjs-advisories-1464 patched version)
archiver ~0.10.0 ➔ ~0.6.1
;Note:
[email protected],(>=0.6.1 <0.8.0) transitively depends on [email protected](a version without vulnerability CVE-2017-16137)
Thank you for your attention to this issue!
Sincerely yours,
Paimon
The text was updated successfully, but these errors were encountered: