Inquirer.js is a popular npm package designed to streamline the creation of interactive command-line user interfaces. Comparing versions 0.1.1 and 0.1.2 reveals a minor update with both versions sharing identical core functionality, dependencies, and development dependencies. Both packages rely on async, charm, and lodash for asynchronous operations, terminal character manipulation, and utility functions respectively. Developers utilize the same suite of testing and build tools for both versions, including chai, grunt, mocha, sinon, and related Grunt plugins. The license remains MIT, and the repository information points to the same GitHub repository. The author and maintainer is Simon Boudrias.
The notable difference lies in the release date and potentially very minor bug fixes or internal improvements between the two versions. Version 0.1.2 was released on May 24, 2013, a mere few days after version 0.1.1, released on May 21, 2013. For developers looking to integrate Inquirer.js into their projects, both versions offer the same core set of features for building engaging CLI interactions. This includes prompting users for input, displaying lists and confirmations, and handling user choices. Developers should use the latest stable version (0.1.2 in this case) as it likely contains the most up-to-date bug fixes and potential performance enhancements while offering the same functionality than the previous one. The tarball URLs indicate the specific package archives available on the npm registry.
All the vulnerabilities related to the version 0.1.2 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.