Inquirer.js is a popular Node.js package offering a suite of interactive command-line user interface tools. Comparing versions 0.5.0 and 0.4.1, several key differences emerge that could influence a developer's choice. Version 0.5.0, released on May 15, 2014, includes an update to the cli-color dependency, moving from version 0.2.2 to version 0.3.2. This might address bugs and add functionalities related to terminal text styling within the prompts. Other dependency upgrades worth a mention are in the async package which went from version 0.2.8 to version 0.8.0.
On the development dependency side, version 0.5.0 upgrades grunt-release to version 0.7.0 and grunt-mocha-test to version 0.10.2. Also, related to the command line tools is the upgrade for grunt-contrib-jshint to version 0.10.0 . These upgrades reflect improvements in the build and testing processes, and using version 0.5.0, should lead to a more streamlined experience. Developers aiming for the latest features and security updates on its tooling will find 0.5.0 an appealing and reliable upgrade. The core functionality for prompting users remains consistent between the two, developers should assess the compatibility of upgraded dependencies with their existing projects before upgrading.
All the vulnerabilities related to the version 0.5.0 of the package
Prototype Pollution in lodash
Versions of lodash before 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep allows a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.12 or later.
Prototype Pollution in lodash
Versions of lodash before 4.17.5 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of Object via __proto__ causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.5 or later.
Prototype Pollution in lodash
Versions of lodash before 4.17.11 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.11 or later.
Regular Expression Denial of Service (ReDoS) in lodash
lodash prior to 4.7.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.7.11.
Regular Expression Denial of Service (ReDoS) in lodash
All versions of package lodash prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
Steps to reproduce (provided by reporter Liyuan Chen):
var lo = require('lodash');
function build_blank(n) {
var ret = "1"
for (var i = 0; i < n; i++) {
ret += " "
}
return ret + "1";
}
var s = build_blank(50000) var time0 = Date.now();
lo.trim(s)
var time_cost0 = Date.now() - time0;
console.log("time_cost0: " + time_cost0);
var time1 = Date.now();
lo.toNumber(s) var time_cost1 = Date.now() - time1;
console.log("time_cost1: " + time_cost1);
var time2 = Date.now();
lo.trimEnd(s);
var time_cost2 = Date.now() - time2;
console.log("time_cost2: " + time_cost2);
Command Injection in lodash
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.