@commitlint/cli version 8.3.0 introduces subtle but important updates compared to version 8.2.0. Primarily, there's a shift in dependency versions, notably within the core @commitlint packages. Dependencies like @commitlint/lint, @commitlint/load, @commitlint/read and @commitlint/format are updated from ^8.2.0 to ^8.3.0, suggesting enhancements or bug fixes within the core linting, loading, reading, and formatting functionalities. The lodash dependency has also been updated from 4.17.14 to 4.17.15, which typically includes minor bug fixes and potential security patches.
Developers should note the updated @commitlint/utils package, moving from ^8.2.0 to ^8.3.0 which likely includes improvements to internal utilities used by commitlint. The pkg-dir dev dependency is bumped from 2.0.0 to 4.2.0. The cross-env dependency is bumped from 5.1.1 to 6.0.0.
The @commitlint/cli package facilitates enforcing commit message conventions, crucial for maintaining a clean and understandable project history, simplifying automation, and improving collaboration. The update signifies an effort to refine these capabilities. Upgrading offers developers the latest improvements in commit message linting, ensuring adherence to established standards, enhancing project maintainability and potentially resolving compatibility issues. Project using commitlint should consider upgrading to benefit from bug fixes, updated utility and potential performance improvements within the core linting process.
All the vulnerabilities related to the version 8.3.0 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.