Inquirer.js version 0.3.3 is a minor update to the popular interactive command-line user interface library, building upon the foundation laid by version 0.3.2. Both versions share the same core dependencies, relying on 'async' and 'lodash' for asynchronous operations and utility functions respectively and 'cli-color' and 'mute-stream' for enhanced command-line styling and output control. Similarly, the development dependencies remain consistent, with tools like 'chai', 'mocha', and 'sinon' ensuring robust testing, and 'grunt' streamlining the build process. This consistency indicates a focus on stability and continuous improvement rather than radical changes between releases.
The primary difference lies in the release date, with version 0.3.3 being published on September 8, 2013, a few days after version 0.3.2's release on September 3, 2013. This suggests that version 0.3.3 likely contains bug fixes, performance enhancements, or minor feature additions that warranted a quick follow-up release.
For developers, the key takeaway is the commitment to stability reflected in the unchanged dependencies. If you're using Inquirer.js, upgrading from 0.3.2 to 0.3.3 is likely a safe and recommended practice, as it should offer improvements without introducing breaking changes. The library as a whole provides a robust toolkit for creating engaging and intuitive command-line interfaces, making it an excellent choice for projects requiring user interaction via the terminal. The MIT license ensures flexibility and freedom for incorporating Inquirer.js into a wide range of projects.
All the vulnerabilities related to the version 0.3.3 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.