Grunt-conventional-github-releaser streamlines the process of creating GitHub releases directly from your Grunt build. Version 0.5.0 builds upon the foundation of version 0.4.0, offering key updates for smoother integration and enhanced functionality. One notable change lies in the updated dependency for conventional-github-releaser, moving from version 0.4.0 to 0.5.0. This likely incorporates the latest improvements and bug fixes from the underlying release automation tool. While the core description of the package remains the same ("Make a new GitHub release using conventional-github-releaser"), developers will benefit from the updated dependencies which ensures compatibility. Both versions share common dependencies like 'chalk' for colorful console output and 'plur' for handling pluralization. The developer tooling including 'grunt', 'grunt-contrib-jshint','grunt-jscs' and more remains consistent .Migrating from version 0.4.0 to 0.5.0 should be straightforward, primarily involving updating the package dependency. Be sure to review the changelog for conventional-github-releaser 0.5.0 to leverage potential new features or address any breaking changes in that underlying package. This Grunt plugin simplifies release management, saving developers valuable time and reducing manual errors.
All the vulnerabilities related to the version 0.5.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.
dot-prop Prototype Pollution vulnerability
Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.
Command Injection in lodash
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
Uncontrolled Resource Consumption in trim-newlines
@rkesters/gnuplot is an easy to use node module to draw charts using gnuplot and ps2pdf. The trim-newlines package before 3.0.1 and 4.x before 4.0.1 for Node.js has an issue related to regular expression denial-of-service (ReDoS) for the .end() method.
