Lodash, a widely-used JavaScript utility library, offers a developer-friendly toolkit for enhancing code consistency, customization, and performance. Examining versions 1.2.0 and 1.1.1 reveals subtle yet important details for developers considering this powerful library. Both versions share the same core description: a utility library designed to promote consistency, customization options, improved performance and useful extras. They are released under the MIT license, and authored by John-David Dalton, reflecting a commitment to open-source principles and a single point of consistent authorship. The source code repository remains constant at GitHub further solidifying the project's commitment to transparency and collaborative development.
The key difference lies in the version number where the update moves from 1.1.1 to 1.2.0 with this minor version increment signifying bug fixes, new features or other improvements. The release dates although very close, 2013-09-04T14:24:07.907Z for v1.1.1 and 2013-09-04T14:24:34.140Z for v1.2.0 do confirm that version 1.2.0. is the latest one and contains the new features.
For developers, choosing between these versions might involve considering if any new minor features are avaiable in 1.2.0 as well as if bugs present in 1.1.1 are fixed.
All the vulnerabilities related to the version 1.2.0 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.