Potential Resource Exhaustion vulnerability in Cronicle's use of Glob

[matthewjhands]

Hello,

The SCA dependency scanning tool where I work and use Cronicle has picked up a "high" vulnerability in the glob dependency of Cronicle, because [email protected] itself has a dependency on [email protected] which has a known memory leak issue, ⁠which at least in theory could lead to a resource exhaustion vulnerability. The Inflight maintainers have indicated that they won't be attempting to fix this bug ⁠because the whole project is deprecated.

I have a question and a feature request:

1. Do you think there is any realistic resource exhaustion vulnerability to Cronicle, given how it uses glob?
2. Is there any chance that Cronicle could be upgraded to use [email protected], ⁠which apparently doesn't leverage inflight please?

Many thanks,
Matt

[jhuckaby]

Hi there!

How weird, NPM audit doesn't catch that vuln at all, nor did I receive a notification from my snyk.io account 🤷🏻‍♂️

Oh well, I just went ahead and removed glob as a dependency entirely. Cronicle v0.9.63 now uses my own glob implementation in pixl-tools (which uses picomatch under the hood).

Fixed in v0.9.63: https://github.com/jhuckaby/Cronicle/releases/tag/v0.9.63

[matthewjhands]

@jhuckaby you are the best. Thanks for getting this fixed so quickly (18 minutes!).

Many thanks and have a lovely Christmas break.

Matt