Webpack CLI version 3.3.3 introduces several updates compared to the previous stable version 3.3.2, enhancing the developer experience and build process. A notable addition is the inclusion of prettier as a direct dependency, suggesting a focus on code formatting and consistency within projects utilizing the CLI. Another changed dependency is the replacement of typedoc-plugin-monorepo with @strictsoftware/typedoc-plugin-monorepo, suggesting a move to a different implementation source for monorepo documentation.
Furthermore, the updated version includes changes to several development dependencies, reflecting improvements in testing, linting, and code quality. bundlesize is updated from version 0.17.0 to 0.17.2. There are some changes to the eslint and typscript related packages, including @typescript-eslint/parser and @typescript-eslint/eslint-plugin going from 1.6.0 to 1.9.0, and eslint-config-prettier going from 4.1.0 to 4.3.0, potentially indicating improvements in static analysis and code style enforcement. The upgrade of lerna from 3.13.4 to 3.14.1 could imply enhancements to the monorepo management capabilities for larger projects. Overall, version 3.3.3 appears to prioritize code quality through formatting and linting improvements and better dependency management making it a recommended upgrade for developers seeking a more refined and robust Webpack CLI experience.
All the vulnerabilities related to the version 3.3.3 of the package
yargs-parser Vulnerable to Prototype Pollution
Affected versions of yargs-parser are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects.
Parsing the argument --foo.__proto__.bar baz' adds a bar property with value baz to all objects. This is only exploitable if attackers have control over the arguments being passed to yargs-parser.
Upgrade to versions 13.1.2, 15.0.1, 18.1.1 or later.
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.
