Lodash-es versions 4.10.0 and 4.9.0 represent incremental updates to this popular JavaScript utility library, offering developers a modular approach to leveraging Lodash's extensive functionality within ES module environments. Both versions maintain the same core description: Lodash exported as ES modules, inheriting the MIT license and utilizing the same Git repository. The author information, including name, email, and URL, also remains constant, indicating continued authorship by John-David Dalton.
The key differentiator between the two versions lies in their release dates. Version 4.10.0 was released on April 11, 2016, three days after version 4.9.0 which came out on April 8, 2016. This timeframe suggests that version 4.10.0 likely includes bug fixes, performance improvements, and potentially minor feature enhancements built upon the foundation of the 4.9.0 release. Developers should upgrade to the newest version to benefit from these improvements. Because these are minor version updates, developers can expect a smooth transition with minimal breaking changes. Focusing on ES module compatibility, lodash-es allows developers to selectively import only the Lodash functions they need, reducing bundle sizes and improving application performance. The availability of both versions through the npm registry makes integration straightforward. Developers are encouraged to consult the Lodash changelog for a detailed breakdown of the specific changes and updates introduced in version 4.10.0.
All the vulnerabilities related to the version 4.10.0 of the package
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
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 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.