@commitlint/cli version 6.1.2 represents a notable update over its predecessor, version 6.1.0, offering developers enhanced tooling for enforcing commit message conventions. A key difference lies in the dependencies. Version 6.1.2 transitions from relying directly on @commitlint/core to leveraging a suite of dedicated packages: @commitlint/lint, @commitlint/load, @commitlint/read, and @commitlint/format. This modularization promotes a more structured and maintainable codebase, allowing for greater flexibility and targeted updates to specific linting functionalities. Developers gain more control over customizing the linting process, selecting only the necessary components for their projects.
Furthermore, @commitlint/cli@6.1.2 sees upgrades in its dependency tree, moving from chalk@2.3.0 to chalk@2.3.1 and lodash.merge@4.6.0 to lodash.merge@4.6.1. While seemingly minor, these updates often incorporate bug fixes and performance improvements, indirectly benefiting developers using the CLI. In the development dependencies, @commitlint/test and @commitlint/utils also see updates to version 6.1.2 in the newer release, ensuring that testing and utility functions are in sync with the core linting functionalities, improving the overall developer experience. Ultimately, these changes reflect a commitment to refining and optimizing the commitlint ecosystem.
All the vulnerabilities related to the version 6.1.2 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.
