Webpack version 1.9.2 is a minor update following the 1.9.1 release, both iterations of the popular module bundler designed to streamline web development workflows. Both versions share the core purpose of packaging CommonJs/AMD modules for browser deployment, enabling developers to split codebases into manageable bundles loaded on demand. They also equip developers with loaders to preprocess diverse file types like JSON, Jade, CoffeeScript, CSS, and LESS.
Examining the dependency lists, both 1.9.1 and 1.9.2 exhibit identical dependencies, development dependencies, and peer dependencies, suggesting that the core functionality and integration points remain consistent. This probably indicates bug fixes and minor improvements without introducing breaking changes or new features. The shared dependencies include essential tools like async for asynchronous operations, clone for object duplication, esprima for JavaScript parsing, and uglify-js for code minification. The devDependencies reveal a strong emphasis on testing and development tooling, featuring mocha for unit testing, eslint for code linting, and loaders for various file types such as css-loader, file-loader, and less-loader. The consistent peer dependency on node-libs-browser ensures compatibility with browser-specific versions of Node.js core modules.
The key difference lies in the release date, with version 1.9.2 released shortly after 1.9.1. This points towards a quick follow-up release likely addressing immediate bug fix or small enhancement. Given the absence of dependency changes, upgrading from 1.9.1 to 1.9.2 should be seamless and recommended to benefit from the latest stability improvements.
All the vulnerabilities related to the version 1.9.2 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.