NYC version 5.1.1 is a patch release focusing on refinements and bug fixes rather than introducing major new features compared to its predecessor, version 5.1.0. Both versions serve as effective code coverage tools especially suited for projects involving subprocesses. Examining the package.json files reveals subtle differences in the development dependencies (devDependencies).
Specifically, tap receives an update, downgrading from version 2.3.5 in 5.1.0 to 2.3.4 in 5.1.1. This suggests potential adjustments or resolutions related to the testing framework used in the development of NYC. While the core functionalities and dependencies remain largely consistent, this change indicates an attention to detail in maintaining a stable and reliable testing environment during the development process.
Developers already utilizing NYC will likely find 5.1.1 a worthwhile upgrade due to these potential improvements in stability and reliability. For developers new to NYC, both versions offer a solid foundation for code coverage analysis, but opting for the latest patch release (5.1.1) ensures benefit of the most up-to-date fixes and refinements, even if the core feature-set stays identical. Either version provides comprehensive coverage reporting, compatibility with standard JavaScript tooling and an easy set up for different environments due to the very limited changes.
All the vulnerabilities related to the version 5.1.1 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.
