NYC version 12.0.0 introduces several noteworthy updates compared to its predecessor, version 11.9.0, impacting developers using the Istanbul command-line interface. In terms of dependencies, istanbul-reports has been updated from version 1.4.0 to 1.4.1, istanbul-lib-coverage sees an update from 1.1.2 to 1.2.0, and similarly, istanbul-lib-instrument has moved from 1.10.0 to version 2.0.2. Finally, istanbul-lib-source-maps updates from 1.2.3 to 1.2.5. These updates across the Istanbul library components suggest improvements in reporting, coverage analysis, instrumentation, and source map handling, potentially leading to more accurate and detailed code coverage insights for developers. The distribution metadata reveals a significant reduction in fileCount from 4743 to 2931 but a smaller reduction in unpackedSize, moving from 14135183 to 12081714. This could indicate changes in the packaging structure, potentially making the installation process cleaner, while still delivering essential functionalities. For developers, these changes translate to a potentially more efficient and reliable code coverage tool. Upgrading to version 12.0.0 likely brings improvements in the core Istanbul libraries, offering enhanced accuracy and reporting. Keep an eye on the changelogs to fully understand the impact for each Istanbul packages and tailor your testing and coverage strategies accordingly. The updated dependencies contribute to a refined experience in measuring and understanding code coverage during testing and development workflows.
All the vulnerabilities related to the version 12.0.0 of the package
Denial of Service in mem
Versions of mem prior to 4.0.0 are vulnerable to Denial of Service (DoS). The package fails to remove old values from the cache even after a value passes its maxAge property. This may allow attackers to exhaust the system's memory if they are able to abuse the application logging.
Upgrade to version 4.0.0 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.
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.
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 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.
