NYC version 5.6.0 introduces subtle but potentially impactful changes compared to its predecessor, version 5.5.0. While the core functionality of NYC as a code coverage tool remains consistent, noticeable differences emerge in the devDependencies section, which are crucial for developers involved in testing and contributing to the library itself.
Specifically, source-map-fixtures sees an upgrade from version 0.4.0 to 2.1.0. This jump indicates significant changes in how source maps are handled within the testing environment, offering improved accuracy, reliability, or potentially introducing new features relevant to source map validation. Developers relying on source maps for debugging or code transformation should pay close attention to this update, as it might affect their testing workflows.
Furthermore, a close examination of the complete dependency graph remains essential. While the immediate dependencies listed might appear unchanged, transitive dependencies (dependencies of dependencies) could have been updated. These updates, although not explicitly listed, can influence overall performance, security, and stability of the library. Therefore, developers are urged to thoroughly review the complete dependency tree within their projects to ensure compatibility and mitigate any potential conflicts arising from these underlying changes.
Beyond these immediate differences, developers should note the release dates. Version 5.6.0 was released on February 4th, 2016, less than two weeks after version 5.5.0 (January 24th, 2016). This proximity suggests that version 5.6.0 might address specific bugs, performance issues, or compatibility concerns identified shortly after the release of 5.5.0. For users of the older version, upgrading to 5.6.0 is highly recommended to benefit from these improvements and ensure a more stable and reliable experience.
All the vulnerabilities related to the version 5.6.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.
