Webpack versions 1.10.0 and 1.9.13, both powerful module bundlers for modern JavaScript applications, share a common foundation for packing CommonJs/AMD modules, enabling code splitting for on-demand loading and offering loader support for various file types such as JSON, Jade, CoffeeScript, CSS, and LESS. Developers familiar with the core functionalities will find a similar experience in both versions.
However, a key distinction lies in the release date, with version 1.10.0 being released on June 27, 2015, slightly later than version 1.9.13, also released on the same day. While the core dependencies in "dependencies" section remain consistent, indicating a stable set of core functionalities, developers should always investigate the specific changes implemented in each version to ensure compatibility with their existing projects and tooling. Examining the detailed changelog from the webpack project documentation or repository commit history is crucial to understand any bug fixes, performance improvements, or new features introduced in the newer 1.10.0 release. These changes, even if seemingly minor, might address specific issues encountered by developers or offer enhanced capabilities for optimizing their webpack configurations. Careful review provides the confidence needed before upgrading.
All the vulnerabilities related to the version 1.10.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.