Webpack version 1.9.0, released on May 10, 2015, introduces updates and refinements compared to its predecessor, version 1.8.11 released on April 29, 2015. Both versions serve as powerful module bundlers, enabling developers to package CommonJS/AMD modules for browser deployment and split codebases into manageable, on-demand bundles. They also maintain support for loaders that preprocess various file types like JSON, Jade, CoffeeScript, CSS, and LESS.
Key differences emerge in the dependency versions. Version 1.9.0 sees updates in development dependencies like eslint, should, css-loader, style-loader, worker-loader, and extract-text-webpack-plugin, reflecting the continuous evolution of the webpack ecosystem and underlying tools. Moreover version 1.9.0 updates clone and introduces supports-color as a dependency. One significant change is the introduction of a peer dependency: node-libs-browser, enabling developers to leverage browser-compatible versions of Node.js core modules within their webpack projects (version 1.8.11 includes this dependency as a direct dependency). These dependency adjustments often translate to enhanced functionalities, bug fixes, and improved performance. While both versions share core functionalities, developers should consider these dependency updates when migrating to version 1.9.0, potentially impacting compatibility with existing configurations. Also, the repository URL changes from a standard HTTP URL to a git+ssh URL in version 1.9.0.
All the vulnerabilities related to the version 1.9.0 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.