NYC version 3.2.0 represents a notable update to the popular code coverage tool, building upon the foundation laid by version 3.1.0. While both versions share the core functionality and purpose of providing robust code coverage analysis, particularly in environments involving subprocesses, key differences emerge in their dependencies and development dependencies. Version 3.2.0 introduces a dependency on the "glob" package (version ^5.0.14), which likely enhances NYC's ability to match file paths using patterns, potentially providing more flexibility in specifying files or folders to include or exclude from coverage analysis. Additionally, it updates the "istanbul" dependency from version 0.3.16 to 0.3.19, incorporating the latest bug fixes and improvements from the underlying coverage engine.
The development dependencies also receive upgrades. Version 3.2.0 adopts "tap" version ^1.3.4 and "standard" version ^5.2.1, while version 3.1.0 used "tap" version ^1.3.0 and "standard" version ^4.5.4. These updates might introduce changes to the testing framework and coding style enforcement, offering developers a smoother testing experience with newer features and potentially stricter code style guidelines.
For developers seeking a reliable code coverage tool, NYC 3.2.0 offers the benefits of updated dependencies and potential enhancements in file matching capabilities via the "glob" package. This version promotes stability through the "istanbul" package and a better developer experience thanks to the new test framework and coding linter versions. Ultimately, this improvement makes NYC 3.2.0 a solid choice for projects aiming to maintain high code quality and comprehensive test coverage.
All the vulnerabilities related to the version 3.2.0 of the package
Prototype Pollution in lodash
Versions of lodash before 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep allows 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.17.12 or later.
Prototype Pollution in lodash
Versions of lodash before 4.17.5 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which 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.17.5 or later.
Prototype Pollution in lodash
Versions of lodash before 4.17.11 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which 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.17.11 or later.
Regular Expression Denial of Service (ReDoS) in lodash
lodash prior to 4.7.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.7.11.
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.