Webpack-cli version 3.3.11 is a minor update to the popular command-line interface for Webpack, a powerful JavaScript bundler. Compared to the previous stable version, 3.3.10, this release includes several notable changes, particularly in the development dependencies which may indicate under the hood improvemnts for developers. Notably, jest was updated from version 24.8.0 to 24.9.0. Babel-preset-jest update to 24.9.0. The @types/jest version was incremented from 24.0.15 to 24.9.1, ensuring improved type safety and developer experience when writing tests. @babel/register and @babel/preset-env were updated from version 7.4.4/7.4.5 to 7.8.3 to benefit from the new features. Also, babel-preset-env was updated to version ^1.7.0 from 1.7.0
These updates suggest improvements in testing capabilities and overall development workflow. While the core dependencies remain the same, indicating no significant changes to the fundamental functionality of the CLI, the updated development dependencies provide a more robust and efficient environment for contributors and potentially lead to more stable releases. Developers working with Webpack and webpack-cli should find this update beneficial for maintaining a modern and reliable development setup. The file size also changed slightly, indicating under the hood changes. The release date was in February 2020, compared to October of 2019 of last stable version.
All the vulnerabilities related to the version 3.3.11 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.
