NYC version 6.1.0 introduces several notable updates for developers seeking a robust code coverage tool. This release, succeeding version 6.0.0, incorporates dependency upgrades that enhance functionality and potentially address underlying issues. One key change is the move from glob version ^6.0.2 to ^7.0.3, potentially improving file matching capabilities and resolving compatibility concerns. Similarly, yargs sees an update from ^4.1.0 to ^4.3.1, likely bringing enhanced command-line argument parsing. Also, micromatch has been updated from "~2.1.6" to "^2.3.7".
A significant addition in version 6.1.0 is the introduction of find-up at ^1.1.2, which probably helps the tool locate configuration files more efficiently. The append-transform dependency is also updated from ^0.2.0 to ^0.4.0 to improve the way transformations are applied during the coverage process.
On the development dependency front, version 6.1.0 upgrades tap from ^2.3.4 to ^5.7.0, offering a more modern testing framework. Furthermore, version 6.0.0 had clear-require at ^1.0.1 but version 6.1.0 removes this library. These changes collectively aim to provide a more stable and feature-rich code coverage experience. Developers upgrading should review their configuration and test suites to ensure compatibility with these updated dependencies. Ultimately, these enhancements position NYC 6.1.0 as a valuable tool for developers seeking accurate and informative code coverage metrics in their projects.
All the vulnerabilities related to the version 6.1.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.
Regular Expression Denial of Service (ReDoS) in micromatch
The NPM package micromatch prior to version 4.0.8 is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in micromatch.braces() in index.js because the pattern .* will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persisted prior to https://github.com/micromatch/micromatch/pull/266. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching.
Regular Expression Denial of Service (ReDoS) in braces
A vulnerability was found in Braces versions prior to 2.3.1. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.
Regular Expression Denial of Service in braces
Versions of braces prior to 2.3.1 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.
Upgrade to version 2.3.1 or higher.
Uncontrolled resource consumption in braces
The NPM package braces fails to limit the number of characters it can handle, which could lead to Memory Exhaustion. In lib/parse.js, if a malicious user sends "imbalanced braces" as input, the parsing will enter a loop, which will cause the program to start allocating heap memory without freeing it at any moment of the loop. Eventually, the JavaScript heap limit is reached, and the program will crash.
Regular Expression Denial of Service (ReDoS) in cross-spawn
Versions of the package cross-spawn before 7.0.5 are vulnerable to Regular Expression Denial of Service (ReDoS) due to improper input sanitization. An attacker can increase the CPU usage and crash the program by crafting a very large and well crafted string.
