Lodash, a popular JavaScript utility library renowned for providing consistency, customization options, enhanced performance, and useful extras, saw a notable update between versions 2.0.0 and 2.1.0. While both versions share the same MIT license and are maintained in the lodash GitHub repository, developers should be aware of the subtle yet potentially impactful differences.
Both versions boast identical descriptions emphasizing Lodash's core value proposition. The author remains John-David Dalton, ensuring continued expertise and guidance. Crucially, both versions provide the same core functionalities that developers rely upon for streamlining JavaScript development: array manipulation, object handling, function composition, and more.
The difference comes with internal improvements and bug fixes. While the provided data doesn't detail the specific changes, the update from 2.0.0 to 2.1.0 suggests that bug fixes, performance enhancements, or minor feature additions were implemented. Developers upgrading should review the complete changelog (available through lodash's official channels or the npm registry) to understand the precise modifications and ensure compatibility with their existing codebases. The relatively short period between the releases, indicates that the update mainly addresses some problems and stability. Given the established reputation of Lodash, developers gain access to a more refined and potentially more efficient toolset by opting for version 2.1.0 over the preceding version. Therefore, upgrading from 2.0.0 to 2.1.0 should be considered, keeping in mind a thorough review of the related changes.
All the vulnerabilities related to the version 2.1.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.