Lodash-es offers the popular Lodash utility library in a modular format, ideal for modern JavaScript development leveraging ES modules. Examining versions 4.3.0 and 4.4.0 reveals subtle but important differences. Both versions maintain the core promise of Lodash: providing a comprehensive suite of functions for simplifying common programming tasks like array manipulation, object handling, function creation, and more. The key benefit for developers is improved performance through tree shaking, as using ES modules allows bundlers to include only the specific Lodash functions your project needs, reducing the final bundle size compared to importing the entire library.
While the core functionality remains consistent, the upgrade from 4.3.0 to 4.4.0 likely includes bug fixes, performance enhancements, and potentially minor API adjustments. Developers should consult the changelog for a complete list of modifications. Although these changes might be small, staying current with the latest version ensures access to the most stable and optimized Lodash-es experience. For new adopters, Lodash-es provides a powerful and flexible toolkit to enhance their code projects. Because of its modularity and ES Module optimization, it could reduce your bundle size when compared to other similar libraries. Understanding the specific differences between versions, especially for ongoing projects, guarantees smooth transitions and optimal performance. This particular version has a MIT license, so it is free to use in commercial projects.
All the vulnerabilities related to the version 4.4.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.
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.
Prototype Pollution in lodash
Versions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The functions pick, set, setWith, update, updateWith, and zipObjectDeep allow a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires manipulating objects based on user-provided property values or arrays.
This vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances.
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.