-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Usage of debug package #353
Comments
That would mean losing support for Node versions prior to v0.11.3. I'm not sure if that's the way to go. Can you provide an example where the debug issue could be exploited in the context of a program using needle? |
Hi, Wanted to check if moving to a debug 4.3.x version would be possible. |
@tomas Hi! That memory leak was fixed in debug 4.3.0 in 2020. There doesn't seem to be any backport of the fix, so this would imply using the 4.x.x version of Upgrading to debug 4.3.x would fix this vulnerability (and also the one mentioned in the original Issue post). |
I think I'm more inclined to replace the debug package with |
It would certainly remove any past and future vulnerabilities from the |
Would you submit a PR for this? 🙏 |
I can try on the weekend but as a disclaimer, I do not know the needle client nor am I very familiar with NodeJS X) |
Replace `debug` package by node:util.debuglog. Fixes #353
Hi @tomas,
One of needle's dependencies is the
debug
package (used solely inneedle.js
).Lately an issue posted in debug package showing there's a critical bug in the package:
User defined window.localStorage.debug could flow into new Regex() function, leading to a Regular Expression Injection.
Since the usage of debug in needle is so minimal, could you switch to using the native
util.debuglog
option?It offers the exact same usage needle needs. It'd also mean one less dependency in needle.
Thank you,
Avishag
The text was updated successfully, but these errors were encountered: