Webpack-cli version 3.2.1 introduces a notable change: the replacement of the 'opencollective' dependency with 'lightercollective'. Both versions 3.2.0 and 3.2.1 aim to provide a command-line interface for webpack, streamlining the configuration and execution of webpack builds. Developers utilizing webpack-cli benefit from tools that simplify tasks such as initializing projects, running builds, and generating configurations through an interactive command-line experience.
Version 3.2.1, released shortly after 3.2.0, likely addresses minor bug fixes or seeks to optimize performance, with the change in dependencies being the primarily notable difference. Both versions share core dependencies like 'chalk' for colored console output, 'yargs' for command-line argument parsing, and 'enhanced-resolve' for module resolution. Also, they offer the same peer dependency for webpack 4.x. Developers relying on opencollective will need to evaluate the implications of lightercollective for their workflow or contribution process. Both versions have robust development dependencies, including testing frameworks (Jest), linting tools (ESLint, TSLint) and continuous integration support (Codecov). This ensures stability and code quality. Developers upgrading should review the release notes to evaluate the impact of this dependency swap.
All the vulnerabilities related to the version 3.2.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.
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.
global-modules-path Command Injection vulnerability
Versions of the package global-modules-path before 3.0.0 are vulnerable to Command Injection due to missing input sanitization or other checks and sandboxes being employed to the getPath function.
