Lodash-es offers a modern, modular approach to the popular Lodash library, tailored for ES module environments, enhancing tree-shaking and reducing bundle sizes in JavaScript projects. Comparing versions 3.6.0 and 3.7.0, while both share the same core purpose – providing utility functions for common programming tasks – the incremental update from 3.6.0 to 3.7.0 likely includes bug fixes, performance improvements, and potentially new features or refined functionalities.
For developers, Lodash-es provides a comprehensive toolkit suitable for various data manipulation and functional programming needs. The library's modular structure allows developers to import specific functions as needed, preventing the inclusion of unused code and optimizing application performance. The shift to ES modules optimizes applications leveraging module bundlers such as Webpack, Rollup, or Parcel. The author, John-David Dalton ensures code quality.
When choosing between the two versions, developers should typically opt for the newer 3.7.0 unless specific compatibility issues arise. Newer versions generally represent the most stable and feature-rich iteration of the library. Reviewing the changelog between versions 3.6.0 and 3.7.0 is recommended for a detailed list of changes and potential impact on existing code. This helps ensure a smooth update and maximizes the benefits of the latest improvements, like improved efficiency and bug fixes.
All the vulnerabilities related to the version 3.7.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.