Webpack version 1.9.1 is a minor release following version 1.9.0, both iterations of a powerful module bundler designed for modern JavaScript applications. These versions empower developers to efficiently manage and package CommonJS/AMD modules for seamless browser deployment. Key features include the ability to split codebases into multiple bundles, enabling on-demand loading and optimized performance. Both versions support a comprehensive suite of loaders, allowing preprocessing of diverse file types such as JSON, Jade, CoffeeScript, CSS, and Less, facilitating a streamlined development workflow.
The core dependencies remain consistent between versions, ensuring stability and reliability for critical functionalities. Similarly, the development dependencies, encompassing tools for testing (Mocha, Should), linting (ESLint), and code coverage (Istanbul, Coveralls), are maintained, indicating a continued focus on code quality and maintainability. The peer dependency on node-libs-browser in both versions specifies compatibility requirements, ensuring proper interaction with browser environment shims.
While the core functionalities and dependencies are largely identical, the primary distinction lies in bug fixes and minor improvements incorporated in version 1.9.1. Developers should upgrade to 1.9.1 to leverage these enhancements and ensure optimal performance and stability within their webpack-powered projects where these fixes and minor improvements can potentially address issues encountered in version 1.9.0. The release dates also highlight the proximity of the releases, suggesting the rapid addressing of any immediate issues, confirming the project's commitment to responsiveness.
All the vulnerabilities related to the version 1.9.1 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.