Webpack-cli 3.3.8 is a minor update to the command-line interface for Webpack, a popular module bundler. Comparing it to the previous stable version, 3.3.7, reveals subtle yet significant changes. The core dependencies remain the same, including 'chalk' for colorful console output, 'yargs' for command-line argument parsing, and 'enhanced-resolve' for module resolution. Developer dependencies, crucial for testing and development workflows, are largely consistent across both versions with one key difference: the commitlint dependency now includes a caret ^, which allows for potentially new minor releases within that version.
A closer look at the dist section shows that 3.3.8 has a slightly larger unpacked size(222755 Bytes) and a different number of files (15) compared to 3.3.7, with 222069 bytes and 14 files, indicating internal adjustments possibly related to new features or bug fixes. Crucially, the release date differs significantly, with version 3.3.8 released on 2019-09-05, after 3.3.7, released on 2019-08-18 effectively confirming it as a newer patch.
For developers, upgrading to webpack-cli 3.3.8 should be relatively seamless, as the core dependencies haven't changed. The minor adjustments may bring performance improvements or bug fixes related to CLI usability. Developers relying on commitlint should be aware of the new caret and make sure the new releases are compatible with their workflow, even though this should not lead to breaking changes.
All the vulnerabilities related to the version 3.3.8 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.
