NYC is a popular code coverage tool designed to seamlessly integrate with subprocesses, providing developers with comprehensive insights into their test coverage. Version 5.2.0 arrived on January 3, 2016, building upon the foundation of version 5.1.1, released just a few days prior on December 30, 2015.
A key difference lies in the dependency updates. Version 5.2.0 upgrades spawn-wrap from version 1.1.0 to 1.1.1 and introduces find-cache-dir at version 0.1.1. On the other end, the win-spawn dependency present in version 5.1.1 has been removed in version 5.2.0 and replaced by the foreground-child dependency, upgraded from 1.3.0 to 1.3.3.
These updates suggest refinements in how NYC handles subprocess interactions and caching mechanisms, potentially improving performance, stability, or compatibility across different environments. While the core functionality remains consistent, developers upgrading to version 5.2.0 should be aware of these dependency changes, particularly if they rely on specific behaviors or integrations tied to spawn-wrap, win-spawn or the newly introduced find-cache-dir. The shift indicates a move towards greater robustness and an improved caching mechanism. Check the changelog for details on specific bug fixes or feature enhancements associated with these dependency updates.
All the vulnerabilities related to the version 5.2.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.
