NYC (Node.js Coverage) is a command-line interface tool designed to instrument your code with coverage statements, run your tests, and output coverage reports. Versions 6.4.3 and 6.4.2 share a core purpose: enabling JavaScript developers to measure the effectiveness of their tests by identifying lines of code that aren't being executed. Looking at their dependencies, both versions rely on the same core tools like glob, yargs, lodash, and istanbul, ensuring a consistent experience with crucial functionality like file matching, argument parsing, utility functions, and coverage reporting. The primary shift lies within the finer details of the development dependencies. Examining the data, the key change between NYC version 6.4.2 and 6.4.3 is an update to the standard-version package, from version 2.2.0 to 2.2.1. standard-version is a utility that automates version bumping and changelog generation, which simplifies the release process. While seemingly minor, this suggests that the newer version contains some adjustments or fixes related to version management. Developers who rely on accurately and automatically updating their project's version numbers and related documentation might find the update useful. Beyond this, the underlying functionality and core dependencies remain consistent, suggesting that the update is more of a maintenance release with potential bug fixes or improvements for the team's release process rather than a major change affecting end-users directly. This upgrade ensures reliable coverage reporting and simplifies the management of project versions, making it a valuable tool in the developer workflow.
All the vulnerabilities related to the version 6.4.3 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.
