Webpack-cli version 3.3.12 introduces some crucial updates and refinements compared to version 3.3.11, directly impacting developers leveraging webpack for their projects. One notable change lies in the updated dependencies, specifically within the core tools that webpack-cli relies on. The 'yargs' dependency sees an upgrade from version 13.2.4 to 13.3.2, bringing potential enhancements in command-line argument parsing and user experience. Similarly, 'interpret' moves from version 1.2.0 to 1.4.0, suggesting improvements in handling different file types and configurations. 'loader-utils' advances from 1.2.3 to 1.4.0, possibly offering better support for webpack loaders and resource processing. Crucially, 'enhanced-resolve', a key dependency for module resolution within webpack, updates from 4.1.0 to 4.1.1, indicating potential bug fixes or improved efficiency in resolving modules. Finally, 'v8-compile-cache' is bumped from 2.0.3 to 2.1.1 potentially improving startup time via improved caching of compiled code. While the developer dependencies remain largely consistent, these underlying updates in core dependencies can contribute to a more stable and performant experience for developers utilizing webpack-cli. Developers should consider these upgrades when planning updates to their webpack configurations to ensure compatibility and realize the potential benefits of improved module resolution, command-line parsing, and overall build performance.
All the vulnerabilities related to the version 3.3.12 of the package
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.
