Lodash-es version 3.9.3 represents a subtle but important update to the popular utility library, building upon the foundation established by version 3.9.2. Both versions offer developers a modular, ES module-compatible build of Lodash, enabling efficient code splitting and reduced bundle sizes for modern JavaScript applications. This makes them ideal for projects leveraging module bundlers like Webpack, Parcel, or Rollup. The core functionality remains consistent, providing a comprehensive suite of tools for array manipulation, object handling, function composition, and more.
The primary distinction lies in potential bug fixes and minor performance improvements introduced in version 3.9.3. While the changelog details for such minor releases can sometimes be sparse, developers should consider upgrading primarily for increased stability and reliability. The choice between versions often boils down to a trade-off. Version 3.9.2, released a couple of days earlier on May 24th, offers a slightly longer track record of real-world usage. Conversely, upgrading to 3.9.3, released on May 26th, provides the benefits of the latest refinements and potential problem resolution, albeit with a slightly shortened production history. Considering using the latest for new projects and evaluate the risks connected to a quick update for the existing ones. Both versions are licensed under the permissive MIT license, granting developers broad freedom in their use within both open-source and commercial projects.
All the vulnerabilities related to the version 3.9.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.
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.