Webpack 1.9.8 represents a minor update over version 1.9.7, offering subtle but potentially relevant changes for developers utilizing this module bundler. Both versions share the same core functionality: packing CommonJs/AMD modules for browser deployment, splitting codebases into bundles for on-demand loading, and supporting loaders for preprocessing diverse file types like JSON, Jade, CoffeeScript, CSS, and LESS. Their dependency and devDependency lists remain almost identical, indicating stability in the underlying build and testing environment. Key areas such as async, clone, esprima, uglify-js and testing frameworks like mocha and eslint stay consistent.
The most notable difference lies in the allowed peer dependency version for node-libs-browser. Version 1.9.7 specifies a range of >= 0.4.0 <=0.5.0, while 1.9.8 broadens this compatibility to >= 0.4.0 <=0.6.0. This adjustment signals that version 1.9.8 is now compatible with newer versions of node-libs-browser, potentially unlocking access to new features or bug fixes within that library. Developers relying on node-libs-browser should consider upgrading to webpack 1.9.8 to leverage this expanded compatibility. If not using this library, the changes are minor and are not really impacting your usage of Webpack. Finally, the release dates indicate a tight development cycle, with 1.9.8 arriving just a few days after 1.9.7, fixing minor bugs and possibly adding small enhancements.
All the vulnerabilities related to the version 1.9.8 of the package
Regular Expression Denial of Service in uglify-js
Versions of uglify-js prior to 2.6.0 are affected by a regular expression denial of service vulnerability when malicious inputs are passed into the parse() method.
var u = require('uglify-js');
var genstr = function (len, chr) {
var result = "";
for (i=0; i<=len; i++) {
result = result + chr;
}
return result;
}
u.parse("var a = " + genstr(process.argv[2], "1") + ".1ee7;");
$ time node test.js 10000
real 0m1.091s
user 0m1.047s
sys 0m0.039s
$ time node test.js 80000
real 0m6.486s
user 0m6.229s
sys 0m0.094s
Update to version 2.6.0 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.
Regular Expression Denial of Service (ReDoS) in braces
A vulnerability was found in Braces versions prior to 2.3.1. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.
Regular Expression Denial of Service in braces
Versions of braces prior to 2.3.1 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.
Upgrade to version 2.3.1 or higher.
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.