@commitlint/cli version 8.3.2 represents a minor update over the preceding version 8.3.1, offering incremental improvements and bug fixes for developers employing commitlint in their projects. Both versions aim to enforce conventional commit message standards, promoting consistency and clarity in project histories. The core functionality remains consistent: linting commit messages against defined rules to improve collaboration and automate changelog generation.
Examining the dependency changes, we see updates in several core @commitlint packages. Specifically, @commitlint/lint, @commitlint/load, @commitlint/read, and @commitlint/format have been bumped to 8.3.2 from previous versions (primarily 8.3.0 or 8.3.1), suggesting internal enhancements or bug fixes within these modules that directly impact the linting, configuration loading, reading of commit messages, and formatting of output, respectively. Developers might notice slightly improved linting accuracy or more informative error messages thanks to these dependency upgrades. Also, cross-env was updated to 6.0.3 form 6.0.0 and string-to-stream to 3.0.1 from 1.1.1, potentially adding subtle improvements and fixes.
While the unpackedSize remains the same, the releaseDate confirms that 8.3.2 is a more recent release, indicating that developers should prioritize this version to benefit from the latest improvements and resolved issues. Therefore, upgrading from 8.3.1 to 8.3.2 provides minor upgrades in stability and functionality. These small changes ultimately contribute to a more reliable and user-friendly experience when integrated into CI/CD pipelines or local development workflows.
All the vulnerabilities related to the version 8.3.2 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.