Grunt-conventional-changelog simplifies changelog generation for projects adhering to AngularJS commit conventions, automating a traditionally manual process. Versions 1.2.1 and 1.2.2 both share core functionality: generating changelogs from Git metadata, employing the conventional-changelog package (version 0.0.17) for parsing commit messages, and providing a Grunt task integration for seamless workflow integration. They rely on common Grunt plugins, including those for linting (jshint), unit testing (nodeunit), and managing npm packages.
However, a notable distinction lies in their release dates. Version 1.2.1 was released on April 3, 2015, while version 1.2.2 followed on May 2, 2015, indicating a bug fix or minor enhancement occurred within that month. Furthermore, there's a subtle difference in the repository URL format. While both point to the same GitHub repository, version 1.2.2 utilizes the "git+" prefix in its repository URL, potentially offering a slightly different method for Git operations or dependency resolution.
Developers leveraging this Grunt plugin benefit from automated changelog generation, ensuring accurate and consistent documentation of project changes. The adherence to AngularJS commit conventions enforces a structured commit message format, leading to more readable and maintainable changelogs. By automating updates, including bug fixes, performance enhancements, and new features, the tool reduces manual effort, saving valuable development time. The integration with popular Grunt tasks makes it a comfortable extension for existing Grunt-based projects.
All the vulnerabilities related to the version 1.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.
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.
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.
semver vulnerable to Regular Expression Denial of Service
Versions of the package semver before 7.5.2 on the 7.x branch, before 6.3.1 on the 6.x branch, and all other versions before 5.7.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.
