Lodash version 4.17.11 arrived on September 12, 2018, succeeding version 4.17.10 released on April 24, 2018. Both versions share the same core characteristics: they are modular utility libraries under the MIT license, maintained within the lodash GitHub repository. John-David Dalton remains the author. Developers familiar with Lodash will find a consistent experience across these versions.
While both versions maintain identical file counts (1049), a minor difference exists in the unpacked size. Version 4.17.11 reports 1,399,577 bytes unpacked, slightly smaller than version 4.17.10's 1,399,800 bytes. This suggests potential optimizations or minor code adjustments contributed to a slightly reduced footprint in the newer version.
For developers deciding which version to use, the choice likely won't drastically impact functionality. Lodash 4.17.11 offers the advantage of incorporating any bug fixes and subtle improvements made since the prior release. Given the minimal size difference, upgrading to the latest patch version, 4.17.11, is generally recommended for leveraging the most up-to-date version of this popular utility library, ensuring stability and potentially benefitting from minor performance tweaks. Check the Lodash changelog for detailed lists of specific changes between releases.
All the vulnerabilities related to the version 4.17.11 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 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.