Webpack version 1.9.9 arrived shortly after 1.9.8, with a release date of May 24, 2015, compared to May 21, 2015. Examining the package data reveals that the core functionality and feature set, as described in the "description" field, remained consistent between the two versions. Both versions packaged CommonJs/AMD modules for the browser, enabling code splitting and on-demand loading. They also offered support for various loaders to preprocess files such as JSON, Jade, CoffeeScript, CSS, and LESS.
A detailed comparison of the dependencies, devDependencies, and peerDependencies sections shows no changes. This strongly suggests that version 1.9.9 was likely a patch release focusing on bug fixes or minor internal adjustments. Developers can anticipate a seamless upgrade from 1.9.8 to 1.9.9, with no breaking changes or new features requiring code modifications. The consistent dependency list signifies that the underlying tooling and loaders remained compatible, maintaining the stability of webpack workflows. For those using node-libs-browser, the peer dependency remains >= 0.4.0 and <=0.6.0. Therefore, upgrading should represent a low-risk maintenance task, ensuring users benefit from any stability improvements incorporated in the newer version.
All the vulnerabilities related to the version 1.9.9 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.