Webpack-cli version 3.3.10 represents a minor update over version 3.3.9, primarily focusing on bug fixes and potential performance improvements rather than introducing major new features. The core dependencies remain consistent between the two versions, ensuring a stable experience for users already familiar with the 3.3.x series. Developers can expect largely unchanged behavior when upgrading. Both versions rely on a solid foundation of tools like chalk for stylized console output, yargs for command-line argument parsing, and enhanced-resolve for module resolution. Development dependencies also remain consistent, indicating a focus on maintaining existing functionality and code quality. These include essential testing and linting tools like jest, eslint, and typescript tooling, confirming a commitment to robust development practices. While a detailed changelog would provide definitive specifics, the stability in dependencies and development tools suggest that the update from 3.3.9 to 3.3.10 is a low-risk upgrade, likely addressing smaller issues and optimizations without requiring significant code modifications for those already using webpack-cli. Developers monitoring for subtle bug fixes or performance enhancements within the existing feature set will find this update relevant. Also, the sizes of the packages are slightly different, but negligibly, 223630 bytes vs 223021 bytes for the previous version. The release date represents an interval of a little more than a month, with the current version release on 2019-10-31.
All the vulnerabilities related to the version 3.3.10 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.
