@commitlint/cli versions 6.1.3 and 6.1.2 are command-line tools designed to lint commit messages, ensuring they adhere to established conventions. This consistency improves project maintainability and collaboration. Both versions share a similar core functionality, relying on dependencies like meow for command-line argument parsing, chalk for colored output, and get-stdin for reading input from stdin. Crucially, they both depend on other @commitlint packages such as @commitlint/lint, @commitlint/load, @commitlint/read, and @commitlint/format, handling the actual linting process, configuration loading, message reading, and formatting of results.
While the core dependencies remain consistent between versions, the key lies in the updated versions of the internal @commitlint/* dependencies in 6.1.3. These likely contain bug fixes, performance improvements, or new rule implementations for commit message validation. The devDependencies also point to upgrades to testing and development tools, suggesting improvements in the library's internal development process and testing suite. Developers upgrading from 6.1.2 to 6.1.3 can expect a potentially more robust and reliable linting experience, possibly with improved performance. The update signifies a focused effort on refinement and bug fixing. The updated @commitlint/test and @commitlint/utils suggest improvements around testing and streamlining utility functions.
All the vulnerabilities related to the version 6.1.3 of the package
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.
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.
Prototype Pollution in lodash.merge
Versions of lodash.merge before 4.6.2 are vulnerable to prototype pollution. The function merge may 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.6.2 or later.
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.
Prototype Pollution in lodash.mergewith
Versions of lodash.mergewith before 4.6.2 are vulnerable to prototype pollution. The function mergeWith may 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.6.2 or later.
Command Injection in lodash
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
