NYC version 5.3.0 introduces several updates that enhance its functionality as a code coverage tool. Key changes focus on improvements in dependency management and the addition of a crucial dependency for more robust functionality. A significant addition is the "read-pkg" dependency at version ^1.1.0, which likely provides improved package.json reading capabilities, potentially impacting how NYC analyzes project configurations. Additionally, it depends on pkg-up version ^1.0.0, not present in the previous version, which allows to find the closest package.json file.
The upgrade also sees a shift in the acceptable version range for "foreground-child," moving from a specific version "1.3.3" in 5.3.0. This might reflect a need for greater flexibility in managing subprocesses and their interaction with the coverage tool.
Both versions share a common set of core dependencies, including "glob," "yargs," "arrify," "mkdirp," "rimraf," "md5-hex," "istanbul," "strip-bom," "micromatch," "source-map," "spawn-wrap," "signal-exit," "resolve-from," "find-cache-dir," "append-transform," "caching-transform," and "convert-source-map," suggesting a stable foundation for core coverage functionality. The developer dependencies like tap, chai, sinon, lodash, any-path, standard, coveralls, zero-fill, is-windows, forking-tap, split-lines, newline-regex, sanitize-filename, source-map-support and source-map-fixtures are identical, indicating a consistent approach to testing and development tooling.
Developers considering upgrading to version 5.3.0 should evaluate their reliance on interactions with package.json files and dependency management to leverage new features and stability improvements. The explicit listing of read-pkg and pkg-up suggests greater control over handling project metadata.
All the vulnerabilities related to the version 5.3.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.
