NYC version 6.5.0 represents a minor update to the popular code coverage tool, building upon the foundation laid by version 6.4.4. While the core functionality of measuring code coverage for subprocesses remains consistent, several dependency adjustments and removals signal subtle improvements and refinements under the hood.
Notably, the dependency list shows that lodash and strip-bom have been removed. This could indicate a performance optimization or a move to more lightweight or specialized utilities for handling specific tasks previously managed by these larger libraries. The version of lodash used in the previous version 6.4.4 had a 4.9.0 version on dependencies and 4.6.1 on devDependencies, version 6.5.0 brought the package up to date with version 4.12.0 in devDependencies.. Developers should be aware of potential behavioral shifts stemming from these changes, particularly if their code relied on specific lodash functions. Other dependencies versions appear to be updated.
For developers considering upgrading, these changes warrant a review of their testing setup. While the core use cases of nyc should remain unaffected, any edge cases or reliance on the removed/modified dependencies could require adjustments to configuration or code. The upgrade promises potential benefits like improved stability, performance, or a leaner dependency footprint, aligning with best practices for modern JavaScript development. The nyc package continues to provide a valuable solution for ensuring code quality and test coverage in Node.js projects.
All the vulnerabilities related to the version 6.5.0 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.
