Method-override is a lightweight npm package allowing developers to simulate HTTP verbs like PUT, PATCH, or DELETE in environments that don't natively support them, such as older browsers or within certain server-side contexts. Comparing versions 2.2.0 and 2.1.3 reveals subtle but important changes, especially concerning dependency management. Both versions share the core functionality of overriding HTTP methods and rely on dependencies like 'vary', 'methods' and 'parseurl'. The key difference lies in the 'debug' dependency. Version 2.2.0 updates it to "~2.0.0" while version 2.1.3 uses "1.0.4". This indicates a potential update in the debugging tools and logging capabilities offered by the package, which could be significant for developers troubleshooting their applications. Both versions leverage the same development dependencies, including 'mocha' for testing, 'istanbul' for code coverage, and 'supertest' for integration testing, ensuring consistent quality control. The package is licensed under the MIT license, promoting open-source usage and modification. Developers considering upgrading from 2.1.3 to 2.2.0 should carefully examine the changes introduced by updating the 'debug' dependency and test the update thoroughly to avoid compatibility issues. The release dates also provide a temporal context, showcasing that version 2.2.0 was released a few weeks after 2.1.3, implying a prompt response to address bugs, compatibility issues, or new features.
All the vulnerabilities related to the version 2.2.0 of the package
method-override ReDoS when untrusted user input passed into X-HTTP-Method-Override header
Affected versions of method-override are vulnerable to a regular expression denial of service vulnerability when untrusted user input is passed into the X-HTTP-Method-Override header.
Update to version 2.3.10 or later
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.