Debug versions 2.1.0 and 2.0.0 are both small debugging utilities, essential for developers needing to add informative logging to their JavaScript projects. Examining the differences, version 2.1.0, released on October 15, 2014, shows a subtle evolution from version 2.0.0, which came out on September 1, 2014. Crucially, both rely on the same version (0.6.2) of the 'ms' dependency, responsible for converting time measurements, ensuring consistent time-related output formatting across these versions.
The more significant change lies in the 'devDependencies'. Version 2.1.0 uses browserify version 6.1.0, upgraded from 5.11.0 in version 2.0.0. Browserify is used internally to bundle the code for distribution in the browser and the developers needed the most recent version for development purposes. Therefore, the application code that depends directly on debug library should see little to no change. Both versions specify "*" for mocha, meaning they will try to use the latest minor and patch of version 5.
For developers considering upgrading from 2.0.0 to 2.1.0, the primary driver is the updated development tooling. There aren't specific new debugging features or API changes, making the upgrade relatively straightforward with minimal risk of breaking existing integrations. This minor update focuses on improving the developer experience and build process, rather than introducing significant functional changes visible to end-users of the library. If you're not actively developing the debug library or contributing to it, but just using it, the upgrade might introduce minimal benefits.
All the vulnerabilities related to the version 2.1.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.