NYC, the Node.js code coverage tool, saw a minor version update from 6.5.0 to 6.5.1. While appearing small, this update includes changes that might be important for developers relying on NYC for robust test coverage reporting. Looking at the dependency changes, the key difference lies in the signal-exit package. Version 6.5.1 upgrades to signal-exit@3.0.0 from signal-exit@2.1.1 in version 6.5.0. The signal-exit package gracefully handles process termination signals, ensuring that necessary cleanup tasks are executed even when the Node.js process is interrupted. This is a critical component for NYC, ensuring that coverage data is persisted correctly regardless of how the test run concludes.
Another change is in the foreground-child package, which upgrades from 1.4.0 to 1.5.1. foreground-child manages child processes. This means version 6.5.1 might offer subtle improvements regarding how spawned processes are managed, potentially leading to more reliable code coverage in complex testing scenarios involving subprocesses. For developers using NYC in environments where processes are frequently spawned or terminated abruptly, this update is likely beneficial. Although the other dependencies for core functionality and development remain the same, these dependency updates likely address bug fixes and improvements over the previous version. Staying up-to-date ensures more reliable coverage reports and smoother integration with the overall testing workflow.
All the vulnerabilities related to the version 6.5.1 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.
