Lodash version 2.0.0 marks an evolution from version 1.3.1, offering subtle refinements and potentially performance enhancements within this popular JavaScript utility library. Both versions maintain the core ethos of providing consistency, customization options, and improved performance for common programming tasks. The fundamental purpose of Lodash remains intact: to streamline data manipulation, object handling, and functional programming paradigms within JavaScript projects.
A key difference lies in the releaseDate, reflecting approximately a ten-day gap between versions. Developers migrating from 1.3.1 to 2.0.0 could anticipate minor adjustments, bug fixes, or performance improvements introduced within this timeframe. Examining the commit history on the linked GitHub repository (https://github.com/lodash/lodash.git) around September 2013 would provide granular insights into the precise changes implemented.
While the overarching description and key attributes (license, author, repository) remain consistent, the updated version suggests an active maintenance cycle. Developers seeking the most current and potentially optimized iteration of Lodash would benefit from using the 2.0.0 release. As a developer, choosing between these versions depends on the project's requirements for stability versus the latest features and improvements. Keep an eye on the official Lodash documentation and changelog for a complete overview of the incremental updates.
All the vulnerabilities related to the version 2.0.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.