@commitlint/cli versions 5.0.1 and 5.0.0 represent minor iterations in a tool designed to lint commit messages, ensuring they adhere to a defined convention. Both versions share a similar core functionality, aiming to improve code contribution quality and project consistency by enforcing structured commit messages. Key dependencies like meow for CLI argument parsing, chalk for stylized console output, lodash for utility functions, get-stdin for reading from standard input, and babel-polyfill for ES5 compatibility remain consistent between the two. The crucial difference lies in the updated @commitlint/core dependency, bumped from version 5.0.0 to 5.0.1, likely containing bug fixes or minor feature enhancements within the core linting logic.
Furthermore, several development dependencies received updates. @commitlint/test jumps from version 4.3.0 to 5.0.1, suggesting significant improvements or additions to the testing suite. Similarly, @commitlint/utils advances from 4.2.1 to 5.0.1, and babel-preset-commitlint from 4.2.1 to 5.0.1 indicating modifications or refinements in utility functions and babel preset used during development. All these updates suggest a focus on improving test coverage, internal tooling, and overall stability. While the core developer experience remains mostly consistent, upgrading to 5.0.1 is recommended to leverage the latest bug fixes, test improvements, and enhanced utilities, ensuring a more robust and reliable commit linting process.
All the vulnerabilities related to the version 5.0.1 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.1 are vulnerable to Prototype Pollution. The function 'merge' may 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.6.1 or later.
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.
Command Injection in lodash
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
Prototype Pollution in lodash.mergewith
Versions of lodash.mergewith before 4.6.1 are vulnerable to Prototype Pollution. The function 'mergeWith' may 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.6.1 or later.
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.
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.
