fix #4837 Upgrade glob dependency to 8.0.3#4941
fix #4837 Upgrade glob dependency to 8.0.3#4941joewagner wants to merge 1 commit intomochajs:masterfrom
Conversation
|
|
|
@joewagner thank you. I don't agree with your description and conclusions. While installing mocha correctly, minimatch ^3.0.4 resolves to v3.1.2 which - as per your description - should not print any vulnerability report. |
|
@juergba Thanks for checking this out. |
If you can fix the failing tests on Windows, then I don't see any drawbacks. |
I don't use windows. I can try to set up a vm and look at this, but it may take me a while to find the time. |
|
@joewagner @juergba Is it okay for me to take over this PR/branch? |
|
@jb2311 yes, it's probably better to open a new PR. I would close this one then. |
Definitely! Thanks for taking this on, and sorry I didn't find time to setup a Windows env. |
|
created this PR: #4970 All the tests passed on my local windows machine. Only difference from this PR is a newer version of glob |
Description of the Change
The minimatch npm package version <=3.0.4 has a security vulnerability explained here: GHSA-f8q6-p94x-37v3
Mocha has the glob package 7.2.0 as a dependency, which in turn has minimatch ^3.0.4 as a dependency
This results in a high security risk warning for consumers of mocha. See #4937 for an example.
This PR changes the glob dependency to 8.0.3 which no longer depends on the insecure version of minimatch.
Alternate Designs
The current glob version is a fixed value (7.2.0), I thought about using the ^ to set it as ^8.0.3 but the other dependencies here are all fixed versions so I'm following suit.
Why should this be in core?
It's not possible to fix #4937 without updating core.
Benefits
Fix security concerns raised in GHSA-f8q6-p94x-37v3
Possible Drawbacks
All tests pass for me, and I see no drawbacks.
Applicable issues
Applicable Issue is #4937
This should be suitable for a patch release.