The webpack-manifest-plugin is a valuable tool for developers using Webpack to generate asset manifests, simplifying the process of managing and referencing bundled files in web applications. Comparing version 0.2.0 with the older stable version 0.0.2, we find that both share similar core attributes, including the same core dependencies like lodash, and development dependencies such as rimraf, jasmine, webpack, css-loader, style-loader, and extract-text-webpack-plugin, indicating a consistent development environment and feature set. Both versions are licensed under the MIT license and maintained by Dane Thurber.
The primary distinction lies in their version and releaseDate. Version 0.2.0 was released on June 7, 2015, approximately two weeks after version 0.0.2, which was released on May 21, 2015. Although seemingly a minor version bump, this difference suggests potential bug fixes, performance improvements, or subtle feature enhancements implemented between the two releases. A developer migrating to the later version should investigate the changes within this delta to ensure compatibility and leverage and improvements. Both versions offer the core functionality of generating asset manifests. Developers should consult the project's repository and documentation for a comprehensive understanding of any modifications between these versions, ensuring informed decision-making for their project needs.
All the vulnerabilities related to the version 0.2.0 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.
