Redux version 0.2.2 and 0.2.1, both early iterations of the now ubiquitous state management library, offer a glimpse into its initial development focused on hot-reloadable Flux architectures. Comparing the two reveals subtle yet noteworthy changes. The key difference lies in the introduction of an "invariant" dependency in version 0.2.2. This addition suggests a focus on enhancing the library's robustness by enforcing runtime checks and ensuring that certain conditions are met, potentially preventing unexpected behavior and facilitating easier debugging for developers.
Both versions share a core set of dependencies suited for React development, including Babel for ES6 transpilation, Lodash for utility functions, and React itself. The development dependencies highlight a commitment to a modern development workflow using tools like Webpack for bundling and hot-reloading capabilities with react-hot-loader, contributing to a faster and more iterative development experience. The presence of ESLint with React plugin showcases a dedication to code quality and consistent styling, aiding collaboration within development teams.
For developers considering these versions, they offer a functional albeit early implementation of Redux. The addition of "invariant" in 0.2.2 might make it a preferable choice for those prioritizing stability and runtime error prevention during development. The provided metadata showcases the focus on leveraging modern tools and practices popular at the time for efficient React development. However, developers should be mindful of the age of these versions and the significant evolution of Redux since then, potentially leading to compatibility issues with newer libraries and patterns. They are best used in legacy projects specifically requiring these versions.
All the vulnerabilities related to the version 0.2.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.
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.
Cross-Site Scripting in react
Versions of react prior to 0.14.0 are vulnerable to Cross-Site Scripting (XSS). The package's createElement function fails to properly validate its input object, allowing attackers to execute arbitrary JavaScript in a victim's browser.
Upgrade to version 0.14.0 or later.