Lodash version 1.0.2 builds upon the solid foundation established by version 1.0.1, offering developers a refined and potentially more robust utility library. While both versions share the same core description – providing consistency, customization, performance enhancements, and extra functionalities – the key difference lies in their release dates. Version 1.0.2 was released on March 30, 2015, a significant update compared to version 1.0.1, which debuted on August 31, 2013. This nearly two-year gap suggests a period of development, bug fixes, and potentially new features integrated into the later version.
For developers, upgrading to 1.0.2 offers the potential benefits of improved performance gleaned from code optimizations, resolutions to known issues present in 1.0.1, and possibly the introduction of new utility functions streamlined for modern JavaScript development practices of 2015. Examining the changelog on the Lodash GitHub repository (linked via the repository.url in the JSON) would be crucial to pinpoint the specific enhancements. If you depend on the speed and efficiency of lodash, you might want to consider the latest version of the library, but be extremely careful with these changes. If you don't have to upgrade, and your code is working fine, it might not be worth it updating.
All the vulnerabilities related to the version 1.0.2 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 before 4.17.5 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of Object via __proto__ causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.5 or later.
Prototype Pollution in lodash
Versions of lodash before 4.17.11 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow 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.11 or later.
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.
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.