The @commitlint/cli package is a valuable tool for developers aiming to enforce consistent and meaningful commit messages within their projects, promoting better collaboration and changelog generation. Comparing versions 8.3.5 and 8.3.4 reveals subtle but relevant changes. The primary difference lies in the updated @commitlint/read and @commitlint/format dependencies in version 8.3.5, bumping them up to ^8.3.4. While seemingly minor, these updates likely address bug fixes, performance improvements, or refined features within the read and format modules that directly impact how commit messages are parsed and presented. Developers should note that while the core dependencies like @commitlint/lint and @commitlint/load, responsible for the actual linting logic and configuration loading, remain functionally compatible (^8.3.5), staying current with newer versions ensures access to the latest enhancements and mitigations.
Furthermore, the unpackedSize of version 8.3.5 is slightly larger (53726 bytes) than version 8.3.4 (53562 bytes), indicating added functionality or data related to the updated dependencies. The release date difference of approximately 12 days highlights a relatively quick iteration cycle, suggesting an active maintenance team responding to user feedback and addressing emerging issues. For developers already using @commitlint/cli, upgrading to 8.3.5 is recommended to benefit from the refinements in commit message processing. New users will naturally start with the latest stable version, benefiting from the most current and robust tooling for consistent commit message enforcement.
All the vulnerabilities related to the version 8.3.5 of the package
yargs-parser Vulnerable to Prototype Pollution
Affected versions of yargs-parser are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects.
Parsing the argument --foo.__proto__.bar baz' adds a bar property with value baz to all objects. This is only exploitable if attackers have control over the arguments being passed to yargs-parser.
Upgrade to versions 13.1.2, 15.0.1, 18.1.1 or later.
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.
Regular Expression Denial of Service (ReDoS) in lodash
All versions of package lodash prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
Steps to reproduce (provided by reporter Liyuan Chen):
var lo = require('lodash');
function build_blank(n) {
var ret = "1"
for (var i = 0; i < n; i++) {
ret += " "
}
return ret + "1";
}
var s = build_blank(50000) var time0 = Date.now();
lo.trim(s)
var time_cost0 = Date.now() - time0;
console.log("time_cost0: " + time_cost0);
var time1 = Date.now();
lo.toNumber(s) var time_cost1 = Date.now() - time1;
console.log("time_cost1: " + time_cost1);
var time2 = Date.now();
lo.trimEnd(s);
var time_cost2 = Date.now() - time2;
console.log("time_cost2: " + time_cost2);
Command Injection in lodash
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
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.