NYC is a command-line interface tool aimed at enhancing code coverage analysis for JavaScript projects, particularly those leveraging subprocesses. Versions 6.4.0 and 6.4.1 share a common core functionality, providing developers with a means to instrument code, collect coverage data, and generate comprehensive reports. These reports allow developers to identify areas of their code that may not be adequately tested, improving the overall quality and reliability of their software.
Both versions depend on a suite of packages, like glob, yargs, and istanbul, ensuring consistent file matching, argument parsing, and coverage instrumentation. Several development dependencies are also identical, including testing frameworks like tap, chai, and sinon, linting tools such as standard, and utilities such as lodash and is-windows. These dependencies allow developers to maintain code quality while writing tests for their projects.
A key difference between the versions lies in their release date, with version 6.4.1 released approximately two weeks after version 6.4.0.. While the change log is not present for both versions, this small gap in release dates suggests that version 6.4.1 likely rolled out with minor bug fixes or dependency updates not drastic enough to change any of the core dependencies. For developers, upgrading from 6.4.0 to 6.4.1 is thus a good idea to ensure they are on the most stable and up-to-date version with the newest minor bug fixes, all while retaining the same overall features and functionalities.
All the vulnerabilities related to the version 6.4.1 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.
