Webpack-cli version 3.3.5 introduces several updates and improvements compared to version 3.3.4. Notably, there are updates in both dependencies and devDependencies, indicating a focus on both runtime stability and developer tooling. Key dependency updates include chalk (2.4.2), yargs (13.2.4) and supports-color(6.1.0), suggesting enhancements in command-line argument parsing and color support. This is interesting because webpack-cli is a command line tool, so improving the experience when used via CLI is important in developer experience.
In the devDependencies, there are upgrades to testing frameworks like jest (24.8.0) along with related dependencies @types/jest and ts-jest, indicating improved testing capabilities. Several linting and code formatting tools such as eslint (5.16.0), prettier (1.18.2), and their associated plugins receive updates, showing a commitment to code quality and consistency. TypeScript support is enhanced with updates to typescript (3.5.2), @typescript-eslint/parser and eslint-plugin and ts-node.
Developers using webpack-cli would benefit from these updates through enhanced command-line functionality, improved code quality checks, and more robust testing tools. The peerDependency remains consistent with webpack 4.x.x in both versions, ensuring compatibility with existing webpack configurations. The release date signifies that version 3.3.5 includes the latest bug fixes and performance improvements available at the time of its release.
All the vulnerabilities related to the version 3.3.5 of the package
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.
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.
Prototype pollution in webpack loader-utils
Prototype pollution vulnerability in function parseQuery in parseQuery.js in webpack loader-utils prior to version 2.0.3 via the name variable in parseQuery.js.
loader-utils is vulnerable to Regular Expression Denial of Service (ReDoS) via url variable
A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the url variable in interpolateName.js. A badly or maliciously formed string could be used to send crafted requests that cause a system to crash or take a disproportional amount of time to process. This issue has been patched in versions 1.4.2, 2.0.4 and 3.2.1.
loader-utils is vulnerable to Regular Expression Denial of Service (ReDoS)
A regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils via the resourcePath variable in interpolateName.js. A badly or maliciously formed string could be used to send crafted requests that cause a system to crash or take a disproportional amount of time to process. This issue has been patched in versions 1.4.2, 2.0.4 and 3.2.1.
