NYC version 5.1.0 introduces several updates and new dependencies compared to version 5.0.1, making it a worthwhile upgrade for developers seeking enhanced functionality and broader tool compatibility for code coverage analysis. Key changes reside primarily in the "dependencies" and "devDependencies" sections, reflecting improvements in the tool's underlying infrastructure and testing capabilities. The dependency updates include: glob with updated minor version from 5.0.14 to 6.0.2, a bug-fixing release of spawn-wrap updated with minor version from 1.0.1 to 1.1.0, and the addition of new dependencies such as arrify, md5-hex, resolve-from, append-transform, caching-transform, showcasing improvements and modular functionalities within dependency management. Developers will benefit from these advancements contributing to more robust code coverage analysis. In "devDependencies," there are also important enhancements that add support for testing. These enhancements include updates to tap, from version 1.3.4 to version 2.3.5 increased functionality for testing coverage of the tap framework. Also dependencies were added such as coveralls, win-spawn, zero-fill, is-windows, forking-tap, split-lines meaning more support for functionalities within different platforms. With the addition of newline-regex, sanitize-filename, source-map-support, source-map-fixtures for testing, it makes it easier for testing developers using code coverage. Overall, version 5.1.0 provides a more comprehensive and versatile toolkit for code coverage.
All the vulnerabilities related to the version 5.1.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.
