Closed garbados closed 4 years ago
Hey @garbados! :wave:
Thanks for opening this issue. Running npm audit fix
seems to resolve most of the potential problems for me, but I'm still seeing these:
I don't think the regex DoS problems will have any effect on us, but I don't know enough about the memory exposure problem to conclusively say it's fine. It looks like we're inheriting that from @dominictarr's level-sublevel, which is unmaintained, so we may need to fix ssb-invite so that it's not running on unmaintained code anymore.
levelup
might only be a devDependency in level-sublevel
? it would still be good to keep it up to date though. subleveldown
is another option, but i don't think it has some key features that level-sublevel
is using, like hooks.
does unmaintained mean, the module is finished so no need to change, or does it mean that this module should be phased out when possible?
does unmaintained mean, the module is finished so no need to change, or does it mean that this module should be phased out when possible?
I think the module should be removed when possible, replaced with subleveldown if we actually need sub-databases in level. See this issue for some more info, it looks like were conflicting bugfixes that caused other bugs so the changes were rolled back and the module was deprecated.
These are all false positives. to be vulnerable to a regexp DoS, you'd have to run a user provided regular expression, which we don't. Also to get the memory exposure, you'd have to have a user request for some size of memory and return it, which we also don't do.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
Installing
ssb-server
in a project,npm
makes a lot of noise:Running
npm audit fix
only fixes some of these vulnerabilities. I invite you to take a look at thenpm audit
output yourself -- it's significant, and doesn't gist well.