Lodash-es version 4.17.10 represents a minor update over its predecessor, version 4.17.9, within the popular lodash library ecosystem tailored for ES module environments. Both versions maintain consistent metadata, including the "Lodash exported as ES modules" description, MIT license, and the original author, John-David Dalton. Crucially, the core functionality and purpose of lodash-es remain unchanged: providing a comprehensive suite of JavaScript utility functions optimized for modular consumption in contemporary JavaScript projects.
While the differences may appear subtle on the surface, developers should note the slight variation in unpackedSize. Version 4.17.10 reports an unpacked size of 628251 bytes, a marginal increase from version 4.17.9's 628247 bytes. This potentially signifies minor bug fixes, performance enhancements, or very small code additions within the expansive lodash codebase, optimized for ES module environments. Also the release date differs for a few hours.
For developers, this iterative update suggests a highly stable and actively maintained library. Upgrading from 4.17.9 to 4.17.10 should be seamless, with minimal risk of introducing breaking changes. While the specific improvements may not be explicitly detailed, the new version provides the confidence of ongoing refinement and continuous improvement within the lodash-es ecosystem. Those focused on maintaining the smallest possible bundle size might want to investigate the exact changes that lead to the 4 bytes increase.
All the vulnerabilities related to the version 4.17.10 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.