React-proxy version 0.6.5 is a minor update to the popular React component proxying library, following closely after version 0.6.4. Both versions, authored by Dan Abramov, share the same core functionality: enabling the hot reloading and live editing of React components without losing their internal state or requiring a full remount. This is crucial for maintaining a smooth development workflow, especially when dealing with complex component hierarchies and intricate state management. The library ensures that developers can quickly iterate on UI changes and component logic, seeing the results instantly in the browser without disrupting the application's current state.
The key specifications, including the dependencies on lodash and development dependencies like babel, webpack, mocha and expect, remain consistent between the two versions, indicating that the core build process and testing infrastructure haven't undergone significant alteration. The negligible time between releases, roughly a day, and the identical dependency declarations suggest that version 0.6.5 is most likely a patch release addressing minor bugs, improvements, or documentation updates detected shortly after the release of 0.6.4.
For developers using react-proxy, upgrading from 0.6.4 to 0.6.5 should be seamless, as no breaking changes seem to be introduced. The library provides an efficient way to introduce hot reloading to a project that uses React 0.13.2 and tools like Babel and Webpack, enhancing developer productivity when editing React components.
All the vulnerabilities related to the version 0.6.5 of the package
Command Injection in lodash
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
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.
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.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.
