Lodash-es is a popular JavaScript library offering utility functions delivered as ES modules. Versions 4.17.4 and 4.17.5 represent incremental improvements, yet understanding their distinctions is crucial for developers leveraging Lodash within modern JavaScript projects.
The primary difference lies in their release dates. Version 4.17.4 was released on December 31, 2016, while 4.17.5 arrived on February 4, 2018. That is a significative time difference and, while the metadata doesn't contain specific changelogs for each version, such a gap suggests that 4.17.5 likely includes bug fixes, performance enhancements, and potentially minor feature additions accumulated over that period.
Developers should favor version 4.17.5 due to its recency. Utilizing the later version provides access to the most up-to-date improvements and remedies known issues present in earlier iterations. Lodash-es, distributed as ES modules, promotes efficient tree shaking by bundlers like Webpack or Rollup, leading to smaller bundle sizes in web applications. This is the key functionality for a developer: reduce the load time optimizing the code. By embracing lodash-es in your project, you streamline common data manipulation tasks and code reducing the development time. Choosing new versions of libraries has to be the default way of acting, and with lodash-es it can avoid bugs.
All the vulnerabilities related to the version 4.17.5 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.