Lodash version 0.5.2 arrives as a refined iteration of the popular utility library, building upon the foundation laid by version 0.5.1 and designed as a drop-in replacement for Underscore.js. Both versions share a core mission: delivering enhanced performance, bug fixes, and a richer feature set compared to its predecessor. For developers familiar with Underscore.js, Lodash offers a seamless transition while unlocking potential gains in efficiency and expressiveness.
The key difference lies in the subtle improvements and refinements incorporated in the newer version. While the core functionality remains consistent, version 0.5.2 likely addresses specific bugs or performance bottlenecks identified in 0.5.1. Developers would benefit from upgrading to 0.5.2 to leverage these fixes and ensure code stability. Both versions developed by John-David Dalton, maintain the same characteristics and the same repository.
The release date difference of a few days indicates a rapid response to user feedback or newly discovered issues. As a practical matter, applications already integrating Lodash 0.5.1 should consider migrating to 0.5.2, but the enhancements are likely not revolutionary and more of a bug fixing and small performance improvements release. For new projects, starting with Lodash 0.5.2 is the recommended approach to take advantage of the most up-to-date version and avoid potential problems present only in the older branch.
All the vulnerabilities related to the version 0.5.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.