Lodash-es, a popular JavaScript utility library offering performant and modular tools, saw a minor version update from 4.17.6 to 4.17.7 on March 7th, 2018. While both versions share the same core functionality, licensing under the MIT license, and maintainership by John-David Dalton, a few subtle differences exist. Developers familiar with lodash will find a seamless transition between versions.
The key difference lies in the unpacked size of the library: version 4.17.7 occupies 628017 bytes of disk space after unpacking, a negligible increase of just 24 bytes compared to version 4.17.6's 627993 bytes. While the file count remains constant at 645, suggesting no major architectural changes, this small size increase indicates minor bug fixes, performance tweaks, or documentation updates within the library's modules. Both of these versions being ES modules allow users to cherry-pick exact functions of lodash that they need instead of the entire library, being a good choice in terms of code size.
Developers should consider upgrading to 4.17.7 as it likely incorporates improvements addressing edge cases or minor inefficiencies present in the previous version. Given the library's modular design, updating to the latest patch version ensures developers benefit from the most stable and optimized code, enhancing the reliability of their applications relying on lodash-es utilities. Furthermore, checking the changelog or release notes associated with version 4.17.7 on the official lodash repository is advisable for complete insight into the specific changes implemented.
All the vulnerabilities related to the version 4.17.7 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.