NYC version 5.5.0 is a minor release of the popular code coverage tool, building upon the foundation laid by version 5.4.0. Both versions share the core functionality of providing excellent support for code coverage, especially in environments involving subprocesses, making them ideal for projects with complex testing needs. They offer a robust suite of dependencies including istanbul for coverage instrumentation, glob and micromatch for file matching, and yargs for command-line argument parsing.
The key change in 5.5.0 lies within the foreground-child dependency, which has been updated from version 1.3.3 to 1.3.5. This may include critical bug fixes or performance improvements relating to managing child processes, which could impact overall stability and reliability of coverage reports, especially for projects using more complex workflows. Both releases maintain a comprehensive set of devDependencies targeted at facilitating testing and development, including tools like tap, chai, sinon, and standard for code quality. The library is licensed under ISC and offers code repository on Github. If you depend on foreground-child then upgrade to NYC version 5.5.0, or be aware of this dependency for any support or bug fixing you need.
All the vulnerabilities related to the version 5.5.0 of the package
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.
