Inquirer.js is a popular npm package offering a suite of interactive command-line user interface tools, simplifying the process of creating engaging CLI applications. Comparing versions 0.1.7 and 0.1.6 reveals subtle changes with practical implications for developers. The core dependencies remain consistent (async, lodash, cli-color, and mute-stream), ensuring compatibility with existing projects. Similarly, the development dependencies – including testing frameworks like Chai, Mocha, and Sinon, along with build tools like Grunt – are unchanged, suggesting a focus on stability and maintaining the existing test suite. The license, repository details, and author information are also identical, emphasizing the project's consistent open-source nature and maintainership.
However, the key difference lies in the release dates. Version 0.1.7 was released on June 14, 2013, while version 0.1.6 was released on June 13, 2013. This one-day gap signifies that version 0.1.7 likely includes bug fixes or minor enhancements implemented shortly after the 0.1.6 release. For developers, upgrading from 0.1.6 to 0.1.7 is recommended to benefit from these potential improvements and ensure the most stable experience, without introducing breaking changes considering equal dependencies. The update is likely focused on improving existing functionality and addressing immediate issues identified in the previous release.
All the vulnerabilities related to the version 0.1.7 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.